[Kernel-packages] [Bug 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"

[craigster0]

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

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

Title:
  laptop sound broken in latest update -- "No output or input devices
  found"

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

Bug description:
  after i installed the latest update for Kubuntu 17.10 my audio devices
  disappeared and i lost the ability to listen to music or play sounds
  on my laptop.  it worked fine before the update!

  (Caveat: sometimes ads or youtube will play through the speakers or
  headphones but it is unpredictable and i have no control over volume
  or muting.)

  the Plasma Audio Volume settings show "No Output Devices Available"
  and "No Input Devices Available".  it worked fine before the last
  update.

  this is a Lenovo P51, a fairly popular laptop for linux. my laptop is
  a high end version with an E3-1505M CPU and "hybrid graphics".

  i do not update the software every day so the problem may have been
  introduced upto two weeks ago, but no earlier then that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 21:38:36 2018
  HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20HHCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET31W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1764980] Re: test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM kernel

[Steve Beattie]

I've now added a check for whether CONFIG_KALLSYMS is enabled in the
running kernel and adjusted the expected test results based on that, in
qrt commit https://git.launchpad.net/qa-regression-
testing/commit/?id=cde457932459a525c75126db8a8d4b7262d4da24 . This
should address this failing test case, though it may need to be modified
to take into account differing behavior for the 4.4 linux-kvm kernel.

** Changed in: linux-kvm (Ubuntu Bionic)
   Status: Incomplete => Invalid

** Changed in: qa-regression-testing
   Status: In Progress => Fix Committed

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

Title:
  test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM
  kernel

Status in QA Regression Testing:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-kvm source package in Bionic:
  Invalid

Bug description:
  test_095_kernel_symbols_missing_proc_modules from
  ubuntu_qrt_kernel_security test failed with 4.15.0-1004-kvm

FAIL: test_095_kernel_symbols_missing_proc_modules 
(__main__.KernelSecurityTest)
kernel addresses in /proc/modules are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1609, in 
test_095_kernel_symbols_missing_proc_modules
self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, 
expected=expected)
  File "./test-kernel-security.py", line 1492, in _check_pK_files
test_function(expected_restricted)
  File "./test-kernel-security.py", line 1525, in 
_095_kernel_symbols_missing_proc_modules
expected)
  File "./test-kernel-security.py", line 1414, in _read_twice
self.assertFalse(0 == int(address, 16), "%s: root saw %s" % (filename, 
address))
AssertionError: /proc/modules: root saw 0x

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4
  ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15
  Uname: Linux 4.15.0-1004-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 18 09:00:43 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1764980/+subscriptions

-- 
Mailing list: https://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 1764040] Re: Synaptics Touchpad not Detected

[Dave Harton]

Hi,

No luck. Still no touchpad :(

I was going to do a clean install of 18.04. Is this an idea?

Cheers

On 25 April 2018 at 20:17, Kai-Heng Feng 
wrote:

> Please try if kernel parameter "i8042.noloop=1" works for you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1764040
>
> Title:
>   Synaptics Touchpad not Detected
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Using Cinnamon on 18.04 Beta 2. (Description:   Ubuntu Bionic Beaver
>   (development branch) Release: 18.04)
>
>   Touchpad not detected. Was also not detected in 17.10 but I thought
>   that this was a Wayland problem, but obviously not...
>
>   $ cat /proc/bus/input/devices
>   I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
>   N: Name="AT Translated Set 2 keyboard"
>   P: Phys=isa0060/serio0/input0
>   S: Sysfs=/devices/platform/i8042/serio0/input/input0
>   U: Uniq=
>   H: Handlers=sysrq kbd event0 leds
>   B: PROP=0
>   B: EV=120013
>   B: KEY=40200 3803078f800d001 fedfffef fffe
>   B: MSC=10
>   B: LED=7
>
>   I: Bus=0003 Vendor=046d Product=c077 Version=0111
>   N: Name="Logitech USB Optical Mouse"
>   P: Phys=usb-:00:04.0-4/input0
>   S: Sysfs=/devices/pci:00/:00:04.0/usb2/2-4/2-4:1.0/
> 0003:046D:C077.0001/input/input1
>   U: Uniq=
>   H: Handlers=mouse0 event1
>   B: PROP=0
>   B: EV=17
>   B: KEY=ff 0 0 0 0
>   B: REL=103
>   B: MSC=10
>
>   I: Bus=0003 Vendor=04f2 Product=b012 Version=0346
>   N: Name="USB2.0 1.3M UVC WebCam : USB2.0"
>   P: Phys=usb-:00:04.1-7/button
>   S: Sysfs=/devices/pci:00/:00:04.1/usb1/1-7/1-7:1.0/input/input2
>   U: Uniq=
>   H: Handlers=kbd event2
>   B: PROP=0
>   B: EV=3
>   B: KEY=10 0 0 0
>
>   I: Bus= Vendor= Product= Version=
>   N: Name="HDA NVidia Mic"
>   P: Phys=ALSA
>   S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input3
>   U: Uniq=
>   H: Handlers=event3
>   B: PROP=0
>   B: EV=21
>   B: SW=10
>
>   I: Bus= Vendor= Product= Version=
>   N: Name="HDA NVidia Headphone"
>   P: Phys=ALSA
>   S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input4
>   U: Uniq=
>   H: Handlers=event4
>   B: PROP=0
>   B: EV=21
>   B: SW=4
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-15-generic 4.15.0-15.16
>   ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
>   Uname: Linux 4.15.0-15-generic x86_64
>   NonfreeKernelModules: nvidia
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version
> k4.15.0-15-generic.
>   ApportVersion: 2.20.9-0ubuntu4
>   Architecture: amd64
>   ArecordDevices:
> List of CAPTURE Hardware Devices 
>card 0: NVidia [HDA NVidia], device 0: ALC663 Analog [ALC663 Analog]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  dave   1249 F pulseaudio
>   Card0.Amixer.info:
>Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 15'
>  Mixer name : 'Realtek ALC663'
>  Components : 'HDA:10ec0663,10431903,0011 HDA:10de0007,10de0101,
> 00100100'
>  Controls  : 31
>  Simple ctrls  : 13
>   CurrentDesktop: X-Cinnamon
>   Date: Sun Apr 15 14:40:09 2018
>   HibernationDevice: RESUME=UUID=5345d639-3d67-4cc1-89bc-acdc9546aa2c
>   InstallationDate: Installed on 2017-12-06 (129 days ago)
>   InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171017.1)
>   Lsusb:
>Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
>Bus 001 Device 003: ID 04f2:b012 Chicony Electronics Co., Ltd 1.3
> MPixel UVC Webcam
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 002 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
>Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   MachineType: ASUSTeK Computer Inc. F5GL
>   ProcFB:
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic
> root=UUID=1ddea34f-fe1f-451d-b88a-5c54b8cafeec ro acpi=off quiet splash
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-15-generic N/A
>linux-backports-modules-4.15.0-15-generic  N/A
>linux-firmware 1.173
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)
>   dmi.bios.date: 11/20/2008
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 213
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: F5GL
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.board.version: 1.0
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK Computer Inc.
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr213:bd11/20/2008:
> svnASUSTeKComputerInc.:pnF5GL:pvr1.0:rvnASUSTeKComputerInc.:rnF5GL:rvr1.0:
> 

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Jay Vosburgh]

I would suggest testing

commit de77ecd4ef02ca783f7762e04e92b3d0964be66b
Author: Mahesh Bandewar 
Date:   Mon Mar 27 11:37:33 2017 -0700

bonding: improve link-status update in mii-monitoring

and

commit d94708a553022bf012fa95af10532a134eeb5a52
Author: WANG Cong 
Date:   Tue Jul 25 09:44:25 2017 -0700

bonding: commit link status change after propose


backported to 4.4.0-120 (in the order above; the second is a fix to the first).

The first patch initially appears in 4.12-rc1, the second in 4.13.

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.asset.tag: 0018880
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1532267] Re: Atheros QCA9565 Bluetooth not recognized

[Daniel van Vugt]

Confirmed by duplicate bug reports.

** Tags added: bionic xenial

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

Title:
  Atheros QCA9565 Bluetooth not recognized

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have installed Ubuntu 14.04 on my Acer Aspire E5-573G, and the
  bluetooth was not recognized, but wifi is working perfectly. This
  problem occurred from kernel 3.19 - 4.4-rc8.

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0803]
   Kernel driver in use: ath9k

  The result of lsusb;
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc.
  Bus 001 Device 005: ID 046d:c534 Logitech, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  8 14:41:21 2016
  InstallationDate: Installed on 2015-12-25 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lmrodrigues   2174 F pulseaudio
   /dev/snd/controlC1:  lmrodrigues   2174 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=898c0089-7a66-4b09-b59b-0953113ce894
  InstallationDate: Installed on 2015-12-25 (15 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire E5-573G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=37df17cf-666c-4aa5-b851-ef8e5f7ce3e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  trusty
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1475639] Re: Atheros QCA9565: No adapter found in bluetooth

[Daniel van Vugt]

Is this still an issue? See also bug 1532267

** Summary changed:

- No adapter found in bluetooth
+ Atheros QCA9565: No adapter found in bluetooth

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

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

Title:
  Atheros QCA9565: No adapter found in bluetooth

Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  Fix Released

Bug description:
  1. the result of `lspci -nnk | grep -iA2 net; lsusb`  is :

  07:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 
Wireless Network Adapter [168c:0036] (rev 01)
Subsystem: XAVi Technologies Corp. Device [1b9a:28a2]
Kernel driver in use: ath9k
  08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
Subsystem: Toshiba America Info Systems Device [1179:f920]
Kernel driver in use: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd 
  Bus 002 Device 002: ID 0930:0227 Toshiba Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  2. the result of usb-devices | awk '/0227/' RS=  is :

  T:  Bus=02 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
  D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0930 ProdID=0227 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
  mike@mikes:~$ usb-devices | awk '/0227/' RS
  awk: fatal: cannot open file `RS' for reading (No such file or directory)

  3. I am using Ubuntu 14.04.2
  4. package manager version is 13.10
  5. Expected to see a bluetooth adapter
  6. says "No adapted found"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-44-generic 3.16.0-44.59~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-44.59~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 17 15:28:44 2015
  InstallationDate: Installed on 2015-04-22 (86 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1618219] Re: Bluetooth driver module doesn't work

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1532267, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1532267
   Atheros QCA9565 Bluetooth not recognized

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

Title:
  Bluetooth driver module doesn't work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Apparently the Ath9k module won't work with Ubuntu 16.04.
  Wireless is just ok.
  Qualcomm Atheros QCA9565 / AR9565 BT 4.0

  T:  Bus=02 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#=  6 Spd=12   MxCh= 0
  D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=300b Rev= 0.02
  C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  A:  FirstIf#= 0 IfCount= 2 Cls=e0(wlcon) Sub=01 Prot=01
  I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
  E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
  I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
  I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
  I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
  I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
  I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
  I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
  E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  danilo 3764 F pulseaudio
   /dev/snd/controlC0:  danilo 3764 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Aug 29 18:28:56 2016
  EcryptfsInUse: Yes
  MachineType: Acer Aspire E5-471
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=17c23581-58a2-4103-89c6-66eff0631645 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA40_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.25:bd01/15/2015:svnAcer:pnAspireE5-471:pvrV3.72:rvnAcer:rnEA40_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-471
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1532267] Re: Atheros QCA9565 Bluetooth not recognized

[Daniel van Vugt]

See also bug 1475639

** Summary changed:

- 168c:0036 [Aspire E5-573G] Bluetooth not recognized
+ Atheros QCA9565 Bluetooth not recognized

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

Title:
  Atheros QCA9565 Bluetooth not recognized

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have installed Ubuntu 14.04 on my Acer Aspire E5-573G, and the
  bluetooth was not recognized, but wifi is working perfectly. This
  problem occurred from kernel 3.19 - 4.4-rc8.

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0803]
   Kernel driver in use: ath9k

  The result of lsusb;
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc.
  Bus 001 Device 005: ID 046d:c534 Logitech, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  8 14:41:21 2016
  InstallationDate: Installed on 2015-12-25 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lmrodrigues   2174 F pulseaudio
   /dev/snd/controlC1:  lmrodrigues   2174 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=898c0089-7a66-4b09-b59b-0953113ce894
  InstallationDate: Installed on 2015-12-25 (15 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire E5-573G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=37df17cf-666c-4aa5-b851-ef8e5f7ce3e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  trusty
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1767258] Re: bluetooth cann't open

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1532267, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

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

** Summary changed:

- bluetooth cann't open
+ Atheros QCA9565 bluetooth hardware not detected

** This bug has been marked a duplicate of bug 1532267
   Atheros QCA9565 Bluetooth not recognized

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

Title:
  Atheros QCA9565 bluetooth hardware not detected

Status in bluez package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I can't open bluetooth in the setting panel,it's gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 12:01:53 2018
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer TravelMate P257-MG
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: TravelMate P257-MG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

For Xenial, when can we expect the Ubuntu-1.157.18 release?

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Incomplete

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

[Shrirang Bagul]

Yes, for Bionic, Redpine will push their FW into upstream linux-
firmware.

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Incomplete

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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

[Kernel-packages] [Bug 1754492] Re: Dell XPS 15 - Turned off Keyboard backlight turns on after resuming from suspend

[Kai-Heng Feng]

Which laptop light do you refer to?

I can't find any PCIe errors from the dmesg in the bug report.

Also, I guess it's time to try Bionic (18.04). The GNOME in 16.04 is
quite old.

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

Title:
  Dell XPS 15 - Turned off Keyboard backlight turns on after resuming
  from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the Dell XPS 15 (2017; 9560) the turned off keyboard backlight
  turns back on following a suspend.

  Ubuntu GNOME

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Linux krypton 4.13.0-36-generic #40~16.04.1-Ubuntu SMP
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 2553 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9def3c5c-92fd-4360-a403-30fc2e7e6a96
  InstallationDate: Installed on 2017-08-14 (207 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 007: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 003: ID 0c45:6713 Microdia
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=2149c19b-fca4-49d2-809b-e28952692af2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1764597] Re: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]

[Kai-Heng Feng]

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu

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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]

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

Bug description:
  System freezes completely, but not all at once. Some windows become
  unresponsive first, then eventually system is totally unresponsive.

  Managed to trigger what appears to be a similar issue when testing
  using Linux 4.17-rc1, but bug reporter did not come up that time.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1648 F pulseaudio
   /dev/snd/controlC0:  user   1648 F pulseaudio
  Date: Mon Apr 16 14:34:20 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: HP HP ENVY x360 Convertible 15m-bq1xx
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=bb7709d6-a6b2-4f7f-9d3b-1245354c6f5a 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.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  StagingDrivers: r8822be
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd11/10/2017:svnHP:pnHPENVYx360Convertible15m-bq1xx:pvr:rvnHP:rn83C6:rvr63.17:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bq1xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1767258] Re: bluetooth cann't open

[Daniel van Vugt]

Please try toggling the switch in the header bar to ON (next to the
minimize/maximize/close buttons).

If that doesn't work then it appears the problem is that the kernel has
not detected your bluetooth hardware (see rfkill.txt above).


** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: gnome-control-center (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/1767258

Title:
  bluetooth cann't open

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't open bluetooth in the setting panel,it's gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 12:01:53 2018
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer TravelMate P257-MG
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: TravelMate P257-MG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Kernel-packages] [Bug 1712038] Re: ubuntu_qrt_kernel_security test_060_nx failed on Trusty ARM64

[Po-Hsu Lin]

Hi Steve,
the result is:

ubuntu@ms10-34-mcdivittB0-kernel:~$ cat /proc/self/personality
0040

ubuntu@ms10-34-mcdivittB0-kernel:~$ uname -a
Linux ms10-34-mcdivittB0-kernel 3.13.0-146-generic #195-Ubuntu SMP Tue Apr 24 
14:56:21 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

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

Title:
  ubuntu_qrt_kernel_security test_060_nx failed on Trusty ARM64

Status in QA Regression Testing:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From the error output, this bug was marked as Failed, instead of being
  skipped:

  NX bit is working ... (skipped: ARM64 older than 4.4 has
  READ_IMPLIES_EXEC personality set) FAIL

  FAIL: test_060_nx (__main__.KernelSecurityTest)
   NX bit is working
   --
   Traceback (most recent call last):
     File "./test-kernel-security.py", line 460, in test_060_nx
   self.assertShellExitEquals(expected, ["./nx-test", "data"])
     File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: Got exit code -11, expected 0
   Command: './nx-test', 'data'
   Output:
   rodata:0x4010c0
   data:  0x4120a8
   bss:   0x4220c8
   brk:   0x20de1010
   rw:0x7f833a1000
   rwx:   0x7f833a
   stack: 0x7fdd19bfd8
   Dump of /proc/self/maps:
   0040-00402000 r-xp  08:02 10096524   
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test
   00411000-00412000 r--p 1000 08:02 10096524   
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test
   00412000-00413000 rw-p 2000 08:02 10096524   
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test
   00413000-00423000 rw-p  00:00 0
   20de1000-20e03000 rw-p  00:00 0  
[heap]
   7f8320c000-7f8322c000 rw-p  00:00 0
   7f8322c000-7f8335f000 r-xp  08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f8335f000-7f8336f000 ---p 00133000 08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f8336f000-7f83373000 r--p 00133000 08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f83373000-7f83375000 rw-p 00137000 08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f83375000-7f83379000 rw-p  00:00 0
   7f83379000-7f83395000 r-xp  08:02 4718835
/lib/aarch64-linux-gnu/ld-2.19.so
   7f83399000-7f8339b000 rw-p  00:00 0
   7f833a-7f833a1000 rwxp  00:00 0
   7f833a1000-7f833a2000 rw-p  00:00 0
   7f833a2000-7f833a4000 r-xp  00:00 0  
[vdso]
   7f833a4000-7f833a5000 r--p 0001b000 08:02 4718835
/lib/aarch64-linux-gnu/ld-2.19.so
   7f833a5000-7f833a7000 rw-p 0001c000 08:02 4718835
/lib/aarch64-linux-gnu/ld-2.19.so
   7fdd17c000-7fdd19d000 rw-p  00:00 0  
[stack]
   Attempting to execute function at 0x4120a8
   If this program seg-faults, the region was enforced as non-executable...

  Compared to other skipped test, it should be marked as OK, like
  PR_SET_SECCOMP works ... (skipped: not available on ARM64) ok

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1712038/+subscriptions

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

[Kernel-packages] [Bug 1767088] Re: regression Aquantia Corp. AQC107 4.15.0-13-generic -> 4.15.0-20-generic ?

[Kai-Heng Feng]

I guess that's because I pulled a bunch of fixes from v4.16 to Bionic
kernel.

I pulled two additional commits from v4.17, please try this kernel:
https://people.canonical.com/~khfeng/lp1767088/

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

Title:
  regression Aquantia Corp. AQC107 4.15.0-13-generic ->
  4.15.0-20-generic ?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Anyone can confirm the atlantic kernel driver is not working with
  bionic 4.15.0-20-generic? The only thing I changed is installing
  kernel and modules 4.15.0-13-generic to get it working with the same
  packages and software. ethtool gives me this info:

  # ethtool 

  diff 4.15.0-13-generic -> 4.15.0-20-generic
  19c19
  < Speed: 1Mb/s
  ---
  > Speed: Unknown!
  26c26
  < Link detected: yes
  ---
  > Link detected: no

  # ethtool -d 

  diff 4.15.0-13-generic -> 4.15.0-20-generic
  4,12c4,12
  < 0x0010: 00 00 00 00 00 c0 64 c8 07 00 00 00 00 04 00 80 
  < 0x0020: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 
  < 0x0030: 00 00 00 00 00 80 0c d9 07 00 00 00 00 04 00 80 
  < 0x0040: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 
  < 0x0050: 00 00 00 00 00 40 68 c8 07 00 00 00 00 04 00 80 
  < 0x0060: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 
  < 0x0070: 00 00 00 00 00 80 c6 cc 07 00 00 00 00 04 00 80 
  < 0x0080: 00 00 00 00 ff 03 00 00 08 00 00 00 04 00 00 00 
  < 0x0090: 00 00 00 00 00 00 7e c8 07 00 00 00 00 10 00 80 
  ---
  > 0x0010: 00 00 00 00 00 c0 ae fc 07 00 00 00 00 04 00 80 
  > 0x0020: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 
  > 0x0030: 00 00 00 00 00 00 b6 fc 07 00 00 00 00 04 00 80 
  > 0x0040: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 
  > 0x0050: 00 00 00 00 00 40 b6 fc 07 00 00 00 00 04 00 80 
  > 0x0060: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 
  > 0x0070: 00 00 00 00 00 00 be fc 07 00 00 00 00 04 00 80 
  > 0x0080: 00 00 00 00 ff 03 00 00 0b 00 00 00 04 00 00 00 
  > 0x0090: 00 00 00 00 00 00 af fc 07 00 00 00 00 10 00 80 
  14c14
  < 0x00b0: 00 00 00 00 00 00 00 00 00 00 33 dc 07 00 00 00 
  ---
  > 0x00b0: 00 00 00 00 00 00 00 00 00 00 b3 fc 07 00 00 00 
  16c16
  < 0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 86 d6 
  ---
  > 0x00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b7 fc 
  19c19
  < 0x0100: 00 00 2b dd 07 00 00 00 00 10 00 80 00 00 00 00 
  ---
  > 0x0100: 00 00 bb fc 07 00 00 00 00 10 00 80 00 00 00 00 
  24c24
  < 0x0150: 02 00 01 00 0e 5a de d2 00 be b0 1f 00 00 00 00 
  ---
  > 0x0150: 02 00 00 00 00 00 00 00 00 be b0 1f 00 00 00 00 

  
  Thanks.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-04 (22 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=ZFS=tank/root 
ro root=ZFS=tank/root boot=zfs zfs.zfs_arc_max=19327352832
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: C226M WS
  dmi.board.vendor: ASRockRack
  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.20:bd11/14/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnC226MWS: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 

[Kernel-packages] [Bug 1767258] [NEW] bluetooth cann't open

[jackchwang]

Public bug reported:

I can't open bluetooth in the setting panel,it's gray.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 12:01:53 2018
InstallationDate: Installed on 2018-03-15 (43 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
InterestingModules: bnep btusb bluetooth
MachineType: Acer TravelMate P257-MG
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA50_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: TravelMate P257-MG
dmi.product.version: V3.72
dmi.sys.vendor: Acer
hciconfig:

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


** Tags: amd64 apport-bug bionic

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

Title:
  bluetooth cann't open

Status in bluez package in Ubuntu:
  New

Bug description:
  I can't open bluetooth in the setting panel,it's gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 12:01:53 2018
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer TravelMate P257-MG
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: TravelMate P257-MG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Kernel-packages] [Bug 1764980] Re: test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM kernel

[Po-Hsu Lin]

I have checked the kernel config for 4.15 linux-kvm, it's true that:
# CONFIG_KALLSYMS is not set

Do you want me to test it with the config enabled? I can build a test
kernel for this.

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

Title:
  test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM
  kernel

Status in QA Regression Testing:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Invalid
Status in linux-kvm source package in Bionic:
  Incomplete

Bug description:
  test_095_kernel_symbols_missing_proc_modules from
  ubuntu_qrt_kernel_security test failed with 4.15.0-1004-kvm

FAIL: test_095_kernel_symbols_missing_proc_modules 
(__main__.KernelSecurityTest)
kernel addresses in /proc/modules are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1609, in 
test_095_kernel_symbols_missing_proc_modules
self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, 
expected=expected)
  File "./test-kernel-security.py", line 1492, in _check_pK_files
test_function(expected_restricted)
  File "./test-kernel-security.py", line 1525, in 
_095_kernel_symbols_missing_proc_modules
expected)
  File "./test-kernel-security.py", line 1414, in _read_twice
self.assertFalse(0 == int(address, 16), "%s: root saw %s" % (filename, 
address))
AssertionError: /proc/modules: root saw 0x

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4
  ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15
  Uname: Linux 4.15.0-1004-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 18 09:00:43 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1764980/+subscriptions

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

[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

[Sandra Ray]

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

I was able to successfully boot the latest 17.10 kernel: linux-
image-4.13.0-39-generic

This issue is resolved.

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

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

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

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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

[Kernel-packages] [Bug 1764980] Re: test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM kernel

[Steve Beattie]

I've reproduced this with the 4.15 linux-kvm kernel. I'm not sure why
it's doing this, though:

  ubuntu@sec-bionic-amd64:~$ sudo cat /proc/modules
  kvm_intel 200704 - - Live 0x
  pata_acpi 12288 - - Live 0x
  ubuntu@sec-bionic-amd64:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1004.4-kvm 4.15.15

with the regular 4.15 kernel, on the same host:

  ubuntu@sec-bionic-amd64:~$ cat /proc/version_signature
  Ubuntu 4.15.0-15.16-generic 4.15.15
  ubuntu@sec-bionic-amd64:~$ sudo head -5 /proc/modules
  nf_conntrack_netlink 40960 0 - Live 0xc05bb000
  nf_conntrack 131072 1 nf_conntrack_netlink, Live 0xc058d000
  libcrc32c 16384 1 nf_conntrack, Live 0xc0556000
  nfnetlink 16384 6 nf_conntrack_netlink, Live 0xc054d000
  snd_hda_codec_generic 73728 1 - Live 0xc0538000

Digging around in /sys/modules, it looks like the
/proc/modules/MODULE/sections/ tree isn't present in linux-kvm, which is
indicating that CONFIG_KALLSYMS is not set. I *think* this is the
difference that is causing the /proc/modules addresses to always be
zero, at least in the 4.15 kernel, but I haven't tracked down codepaths
enough to ensure that's the case.

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

Title:
  test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM
  kernel

Status in QA Regression Testing:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Invalid
Status in linux-kvm source package in Bionic:
  Incomplete

Bug description:
  test_095_kernel_symbols_missing_proc_modules from
  ubuntu_qrt_kernel_security test failed with 4.15.0-1004-kvm

FAIL: test_095_kernel_symbols_missing_proc_modules 
(__main__.KernelSecurityTest)
kernel addresses in /proc/modules are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1609, in 
test_095_kernel_symbols_missing_proc_modules
self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, 
expected=expected)
  File "./test-kernel-security.py", line 1492, in _check_pK_files
test_function(expected_restricted)
  File "./test-kernel-security.py", line 1525, in 
_095_kernel_symbols_missing_proc_modules
expected)
  File "./test-kernel-security.py", line 1414, in _read_twice
self.assertFalse(0 == int(address, 16), "%s: root saw %s" % (filename, 
address))
AssertionError: /proc/modules: root saw 0x

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4
  ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15
  Uname: Linux 4.15.0-1004-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 18 09:00:43 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1764980/+subscriptions

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

[Kernel-packages] [Bug 1767124] Re: bluetoothd crashed with SIGILL

[Daniel van Vugt]

I can't seem to find any existing reports of this crash. All I can tell
is that it looks like Ubuntu 16.04...

Please help us to debug it further by:

1. Applying the workaround from bug 994921.

2. Look in /var/crash for .crash files and when found run:
   ubuntu-bug /var/crash/YOURFILE.crash

3. Tell us here the ID of the newly-created bug.

** Tags added: xenial

** Summary changed:

- bluetoothd crashed with SIGILL
+ bluetoothd crashed with SIGILL in agent_get() from adapter_register()

** Changed in: bluez (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/1767124

Title:
  bluetoothd crashed with SIGILL in agent_get() from adapter_register()

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  systemctl status bluetooth.service 
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 
2min 25s ago
   Docs: man:bluetoothd(8)
Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, 
signal=ILL)
   Main PID: 1458 (code=dumped, signal=ILL)
 Status: "Running"

  Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service...
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37
  Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service.
  Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server
  Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 
initialized
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, 
code=dumped, status=4/ILL
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed 
state.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 
'core-dump'.
  Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated 
too quickly.
  Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service.

  sudo gdb /usr/lib/bluetooth/bluetoothd
  ...
  Program received signal SIGILL, Illegal instruction.
  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  267 src/agent.c: Datei oder Verzeichnis nicht gefunden.
  (gdb) bt
  #0  agent_get (owner=owner@entry=0x0) at src/agent.c:267
  #1  0x555d861b in adapter_register (adapter=0x5587fed0) at 
src/adapter.c:7434
  #2  read_info_complete (status=, length=, 
param=, user_data=0x5587fed0) at src/adapter.c:7897
  #3  0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, 
status=, opcode=opcode@entry=4, index=index@entry=0, 
length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261
  #4  0x5560311c in can_read_data (io=, 
user_data=0x55879ef0) at src/shared/mgmt.c:353
  #5  0x5560ee25 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
  #6  0x77b1004a in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x77b10712 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687

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

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

[Kernel-packages] [Bug 1643242] Re: ASUS ROG G752 ELAN1203:00 04F3:301E Touchpad detected but not working

[Christopher M. Penalver]

jeremyayerst, this report is closed. Hence, it will help immensely if you use 
the computer the problem is reproducible with, and provide necessary debugging 
logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

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

Title:
  ASUS ROG G752 ELAN1203:00 04F3:301E Touchpad detected but not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Model: Laptop ASUS ROG G752 VM
  dual boot with Windows 10; security boot disabled; touchpad activated in uefi

  Touchpad: Name "ELAN1203:00 04F3:301E Touchpad" (see dmesg.txt)

  OS: Ubuntu 4.8.0-27.29-generic 4.8.1 (also tried 4.4.0 and some
  others)

  Symptoms:
  - Touchpad seems to be correctly recognized (see dmesg.txt and Xorg.0.log) 
but doesn't work.
  - evtest: no action on touchpad gets recognized (see evtest.txt)
  - synaptics driver shows some messages regarding "invalid pressure range" and 
"invalid finger width range" (see Xorg.0.log)

  At the moment I use a logitech usb mouse (see dmesg.txt/Xorg.0.log). I
  really want to use only Linux on my machine and banish windows from it
  so any help would be very appreciated! ;-)

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

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

[Kernel-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

[Christopher M. Penalver]

** Tags added: bionic

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The disabled touchpad of my Thinkpad T450s sometimes triggers a click
  lock when I touch it with my palm. This is typical when I'm reaching
  to click the trackpoint's (red pointing stick) left button.

  Reproduction steps:
  1. Disable the touchpad via Ubuntu's "Mouse & Touchpad" setting.

  2. Place and hold two fingers in contact with the touchpad.

  3. Click then release the trackpoint's left button once while the
  cursor is on the desktop area. Then immediately move the cursor with
  the pointing stick.

  4. If the click lock effect gets triggered, a selection would have
  been made and dragged on the desktop area. If the click lock doesn't
  happen, repeat step 3.

  The evtest log on the trackpoint:
  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  This issue doesn't happen with Windows. I can confirm it happens on
  Ubuntu v17/v16, Kubuntu, Ubuntu Mate, Xubuntu, Lubuntu, Linux Mint,
  Fedora, and Open Suse.

  Also, the issue doesn't occur on older thinkpad models which doesn't
  use the same clickpad, e.g. T430 or X230.

  WORKAROUND: Execute at a terminal:
  sudo rmmod psmouse && sudo modprobe psmouse proto=imps

  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/16/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET64WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX001LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET64WW(1.28):bd03/16/2017:svnLENOVO:pn20BX001LUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX001LUS
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1764597] Re: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]

[Jeremy Ong]

Issue still occurring in 4.17-rc2.

Which mailing list should I email with the bug report? I have no idea
what the actual cause of this issue is.

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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]

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

Bug description:
  System freezes completely, but not all at once. Some windows become
  unresponsive first, then eventually system is totally unresponsive.

  Managed to trigger what appears to be a similar issue when testing
  using Linux 4.17-rc1, but bug reporter did not come up that time.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1648 F pulseaudio
   /dev/snd/controlC0:  user   1648 F pulseaudio
  Date: Mon Apr 16 14:34:20 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: HP HP ENVY x360 Convertible 15m-bq1xx
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=bb7709d6-a6b2-4f7f-9d3b-1245354c6f5a 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.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  StagingDrivers: r8822be
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd11/10/2017:svnHP:pnHPENVYx360Convertible15m-bq1xx:pvr:rvnHP:rn83C6:rvr63.17:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bq1xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"

[craigster0]

Yes, i should be able to test with the v4.16 kernel.  I'll try to do
that tonight.

I'm sorry I didn't see your note earlier!

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

Title:
  laptop sound broken in latest update -- "No output or input devices
  found"

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

Bug description:
  after i installed the latest update for Kubuntu 17.10 my audio devices
  disappeared and i lost the ability to listen to music or play sounds
  on my laptop.  it worked fine before the update!

  (Caveat: sometimes ads or youtube will play through the speakers or
  headphones but it is unpredictable and i have no control over volume
  or muting.)

  the Plasma Audio Volume settings show "No Output Devices Available"
  and "No Input Devices Available".  it worked fine before the last
  update.

  this is a Lenovo P51, a fairly popular laptop for linux. my laptop is
  a high end version with an E3-1505M CPU and "hybrid graphics".

  i do not update the software every day so the problem may have been
  introduced upto two weeks ago, but no earlier then that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 21:38:36 2018
  HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20HHCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET31W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1767234] [NEW] Issues on inital boot where WiFi Network card (BCM 4312) is "not ready" and will not function. A force in the terminal to "sudo modprobe wl" forces the adapter to

[Dallas Fouse]

Public bug reported:

Ubuntu 16.04.04 LTS

Wireless LAN fails to operate stating "device not ready" on some initial
start ups.  Can force the issue correct by opening Terminal and entering
"sudo modprobe wl".

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: i386
CurrentDesktop: Unity
Date: Thu Apr 26 20:31:12 2018
InstallationDate: Installed on 2018-04-24 (2 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial

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

Title:
  Issues on inital boot where WiFi Network card (BCM 4312) is "not
  ready" and will not function.  A force in the terminal to "sudo
  modprobe wl" forces the adapter to start.  This issue is intermittent
  and does not arise on all boots of O/S.

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.04 LTS

  Wireless LAN fails to operate stating "device not ready" on some
  initial start ups.  Can force the issue correct by opening Terminal
  and entering "sudo modprobe wl".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Apr 26 20:31:12 2018
  InstallationDate: Installed on 2018-04-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1052933] Re: Kernel oops -- IP: [] ttm_bo_mem_put+0x20/0x30 [ttm] (radeon) 3.2.0-30 update

[Bug Watch Updater]

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

Title:
  Kernel oops -- IP: [] ttm_bo_mem_put+0x20/0x30 [ttm]
  (radeon) 3.2.0-30 update

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  BUG: unable to handle kernel NULL pointer dereference at 000c
  Sep 19 09:19:39 gruber-precise-laptop kernel: [   22.039837] IP: [] 
ttm_bo_mem_put+0x20/0x30 [ttm]

  Consistently cannot sucessfully boot linux-image-3.2.0-30-generic-pae
  included in the last update. 3.2.0-29-generic-pae boots fine. Was able
  to ssh into system to collect this information.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
  Uname: Linux 3.2.0-29-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC268 Analog [ALC268 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC268 Analog [ALC268 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gruber 2491 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xce40 irq 16'
     Mixer name : 'Realtek ALC268'
     Components : 'HDA:11c11040,11790001,00100200 
HDA:10ec0268,1179ff68,0013'
     Controls  : 16
     Simple ctrls  : 9
  Date: Wed Sep 19 09:31:58 2012
  HibernationDevice: RESUME=UUID=ad1901db-1bd6-44e1-a32c-e18e3031d048
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120319)
  MachineType: TOSHIBA Satellite L355D
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae 
root=UUID=f9e1e22a-3447-41cd-b809-2cb180ab7e94 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-29-generic-pae N/A
   linux-backports-modules-3.2.0-29-generic-pae  N/A
   linux-firmware1.79.1
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2009
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.90
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.90:bd06/04/2009:svnTOSHIBA:pnSatelliteL355D:pvrPSLE0U-01000R:rvnTOSHIBA:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite L355D
  dmi.product.version: PSLE0U-01000R
  dmi.sys.vendor: TOSHIBA

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

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

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

[bugproxy]

--- Comment From chngu...@us.ibm.com 2018-04-26 20:38 EDT---
- We have decided to replace the qlogic by Emulex.
- Apply the new kernel patch in 208.
- add the slub_debug=FZPU
System is up with latest kernel and ready now.
root@boslcp3:~# uname -a
Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 
ppc64le ppc64le ppc64le GNU/Linux
root@boslcp3:~# cat /proc/cmdline
root=UUID=bab108a0-d0a6-4609-87f1-6e33d0ad633c ro slub_debug=FZPU splash quiet 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
root@boslcp3:~#

--- Comment From chngu...@us.ibm.com 2018-04-26 20:39 EDT---
FYI: We are doing the migration between boslcp3 & boslcp4 using guest boslcp3g1 
at this moment. Feel free to add more stress on system.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = 

[Kernel-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

[Rashi]

Hi, I just tested the issue with Ubuntu 18.04 LTS which using Linux
kernel v4.15.0-20, and unfortunately the issue still exists.

I wonder if you can compare the ubuntu kernel code with kernel from
fedora or arch linux since they have no issue.

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The disabled touchpad of my Thinkpad T450s sometimes triggers a click
  lock when I touch it with my palm. This is typical when I'm reaching
  to click the trackpoint's (red pointing stick) left button.

  Reproduction steps:
  1. Disable the touchpad via Ubuntu's "Mouse & Touchpad" setting.

  2. Place and hold two fingers in contact with the touchpad.

  3. Click then release the trackpoint's left button once while the
  cursor is on the desktop area. Then immediately move the cursor with
  the pointing stick.

  4. If the click lock effect gets triggered, a selection would have
  been made and dragged on the desktop area. If the click lock doesn't
  happen, repeat step 3.

  The evtest log on the trackpoint:
  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  This issue doesn't happen with Windows. I can confirm it happens on
  Ubuntu v17/v16, Kubuntu, Ubuntu Mate, Xubuntu, Lubuntu, Linux Mint,
  Fedora, and Open Suse.

  Also, the issue doesn't occur on older thinkpad models which doesn't
  use the same clickpad, e.g. T430 or X230.

  WORKAROUND: Execute at a terminal:
  sudo rmmod psmouse && sudo modprobe psmouse proto=imps

  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/16/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET64WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX001LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET64WW(1.28):bd03/16/2017:svnLENOVO:pn20BX001LUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX001LUS
  

[Kernel-packages] [Bug 1764980] Re: test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM kernel

[Steve Beattie]

Hi Po-Hsu,

I'm not sure why this test is failing on linux-kvm. I've modified the
test in question to dump the contents of /proc/modules when the test
fails in qrt commit https://git.launchpad.net/qa-regression-
testing/commit/?id=b47b677b9f99af9539558044ccdb9b4769f1732e ; if we can
get a re-run of the tests with a version of qrt that includes that
commit, that give me more information as to what's going wrong.

We're not seeing this with the generic kernel, so marking that invalid.

Thanks!

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

** Changed in: qa-regression-testing
   Status: New => In Progress

** Changed in: qa-regression-testing
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

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

Title:
  test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM
  kernel

Status in QA Regression Testing:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Invalid
Status in linux-kvm source package in Bionic:
  Incomplete

Bug description:
  test_095_kernel_symbols_missing_proc_modules from
  ubuntu_qrt_kernel_security test failed with 4.15.0-1004-kvm

FAIL: test_095_kernel_symbols_missing_proc_modules 
(__main__.KernelSecurityTest)
kernel addresses in /proc/modules are zeroed out
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1609, in 
test_095_kernel_symbols_missing_proc_modules
self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, 
expected=expected)
  File "./test-kernel-security.py", line 1492, in _check_pK_files
test_function(expected_restricted)
  File "./test-kernel-security.py", line 1525, in 
_095_kernel_symbols_missing_proc_modules
expected)
  File "./test-kernel-security.py", line 1414, in _read_twice
self.assertFalse(0 == int(address, 16), "%s: root saw %s" % (filename, 
address))
AssertionError: /proc/modules: root saw 0x

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4
  ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15
  Uname: Linux 4.15.0-1004-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 18 09:00:43 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1764980/+subscriptions

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

[Kernel-packages] [Bug 1712038] Re: ubuntu_qrt_kernel_security test_060_nx failed on Trusty ARM64

[Steve Beattie]

Hi Po-Hsu,

Sorry this has taken so long to get on my radar.

On a trusty arm64 system, can you report on the output of
/proc/self/personality? At one point, IIRC, it was setting itself to
READ_IMPLIES_EXEC, which caused the ./nx-test executions to succeed when
they should have SIGSEGV'ed (exiting with return code -11/139).

For the read-implies-exec cases (nx-test-rie), stack and other data
segments are marked as executable as well, so those should succeed.

I will go ahead and mark arm64 as expecting normal results non-
executable data segments in QRT, and we can see what breaks there.

Thanks!

** Changed in: qa-regression-testing
   Status: New => In Progress

** Changed in: qa-regression-testing
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  ubuntu_qrt_kernel_security test_060_nx failed on Trusty ARM64

Status in QA Regression Testing:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From the error output, this bug was marked as Failed, instead of being
  skipped:

  NX bit is working ... (skipped: ARM64 older than 4.4 has
  READ_IMPLIES_EXEC personality set) FAIL

  FAIL: test_060_nx (__main__.KernelSecurityTest)
   NX bit is working
   --
   Traceback (most recent call last):
     File "./test-kernel-security.py", line 460, in test_060_nx
   self.assertShellExitEquals(expected, ["./nx-test", "data"])
     File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: Got exit code -11, expected 0
   Command: './nx-test', 'data'
   Output:
   rodata:0x4010c0
   data:  0x4120a8
   bss:   0x4220c8
   brk:   0x20de1010
   rw:0x7f833a1000
   rwx:   0x7f833a
   stack: 0x7fdd19bfd8
   Dump of /proc/self/maps:
   0040-00402000 r-xp  08:02 10096524   
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test
   00411000-00412000 r--p 1000 08:02 10096524   
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test
   00412000-00413000 rw-p 2000 08:02 10096524   
/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test
   00413000-00423000 rw-p  00:00 0
   20de1000-20e03000 rw-p  00:00 0  
[heap]
   7f8320c000-7f8322c000 rw-p  00:00 0
   7f8322c000-7f8335f000 r-xp  08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f8335f000-7f8336f000 ---p 00133000 08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f8336f000-7f83373000 r--p 00133000 08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f83373000-7f83375000 rw-p 00137000 08:02 4718846
/lib/aarch64-linux-gnu/libc-2.19.so
   7f83375000-7f83379000 rw-p  00:00 0
   7f83379000-7f83395000 r-xp  08:02 4718835
/lib/aarch64-linux-gnu/ld-2.19.so
   7f83399000-7f8339b000 rw-p  00:00 0
   7f833a-7f833a1000 rwxp  00:00 0
   7f833a1000-7f833a2000 rw-p  00:00 0
   7f833a2000-7f833a4000 r-xp  00:00 0  
[vdso]
   7f833a4000-7f833a5000 r--p 0001b000 08:02 4718835
/lib/aarch64-linux-gnu/ld-2.19.so
   7f833a5000-7f833a7000 rw-p 0001c000 08:02 4718835
/lib/aarch64-linux-gnu/ld-2.19.so
   7fdd17c000-7fdd19d000 rw-p  00:00 0  
[stack]
   Attempting to execute function at 0x4120a8
   If this program seg-faults, the region was enforced as non-executable...

  Compared to other skipped test, it should be marked as OK, like
  PR_SET_SECCOMP works ... (skipped: not available on ARM64) ok

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1712038/+subscriptions

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

[Kernel-packages] [Bug 1762844] boslcp3g3 xml

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 
EDT---


** Attachment added: "boslcp3g3 xml"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127942/+files/boslcp3g3.dumpxml

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] dmesg output 0418

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-18 12:01 
EDT---


** Attachment added: "dmesg output 0418"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127938/+files/dmesg.201804181042

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] dmesg logs from xmon prompt_boslcp3

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-16 01:31 
EDT---


Attached dl logs from xmon pormpt _boslcp3

** Attachment added: "dmesg logs from xmon prompt_boslcp3"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127937/+files/dmesg_xmon_boslcp3.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  

[Kernel-packages] [Bug 1762844] boslcp3 crashed_used X from xmon prompt

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:22 
EDT---


Attached consolel logs for step(3) & step(4)

** Attachment added: "boslcp3 crashed_used X from xmon prompt"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127944/+files/boslcp3_usedX_xmonprompt.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c 

[Kernel-packages] [Bug 1762844] op-buid instructions for patched skiroot build

[bugproxy]

--- Comment on attachment From mauri...@br.ibm.com 2018-04-26 14:00 
EDT---


Attaching the instructions to build skiroot/skiboot/Petitboot/all with op-build
(in this case, a patched skiroot's kernel -- zImage.epapr),  per Dwip's request.

Hopefully this might help others in the future.

(In reply to comment #203)
> The skiroot kernel build is available at:
>   
> http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/skiroot/bz166588/zImage.
> epapr_4.15.14-openpower1.bz166588c132

** Attachment added: "op-buid instructions for patched skiroot build"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127947/+files/file_166588.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = 

[Kernel-packages] [Bug 1762844] console log

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-20 20:08 
EDT---


** Attachment added: "console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127939/+files/boslcp3.0420.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] boslcp3_host reboots multiple times

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:24 
EDT---


Attached boslcp3 host console logs for step (5)

** Attachment added: "boslcp3_host reboots multiple times"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127945/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] 

[Kernel-packages] [Bug 1762844] boslcp3g4 xml

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:31 
EDT---


** Attachment added: "boslcp3g4 xml"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127943/+files/boslcp3g4.dumpxml

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] qla2xxx version 10.00.00.04-k

[bugproxy]

--- Comment (attachment only) From dougm...@us.ibm.com 2018-04-26 10:51 
EDT---


** Attachment added: "qla2xxx version 10.00.00.04-k"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127946/+files/qla2xxx-10.00.00.04-k.tgz

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c 

[Kernel-packages] [Bug 1762844] boslcp3g1 xml

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 
EDT---


** Attachment added: "boslcp3g1 xml"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127941/+files/boslcp3g1.dumpxml

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] sol console log

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-21 17:04 
EDT---


** Attachment added: "sol console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127940/+files/boslcp3.0421.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] Host console log

[bugproxy]

--- Comment on attachment From chngu...@us.ibm.com 2018-04-13 17:17 
EDT---


The full log of the Host during couple reboot, start test on guest then system 
drop into xmon.

** Attachment added: "Host console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127936/+files/boslcp3.0413.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c 

[Kernel-packages] [Bug 1762844] boslcp3_crash_aprl13

[bugproxy]

--- Comment (attachment only) From indira.pr...@in.ibm.com 2018-04-13 03:24 
EDT---


** Attachment added: "boslcp3_crash_aprl13"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127935/+files/boslcp3_crash_aprl13.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c 

[Kernel-packages] [Bug 1762844] boslcp3 host crash console logs

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-12 14:25 
EDT---


Attached boslcp3 host crash console logs

** Attachment added: "boslcp3 host crash console logs"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127934/+files/host_crash_boslcp3.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  

[Kernel-packages] [Bug 1762844] Second attempt of host reboot_boslcp3

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-12 11:13 
EDT---


Attached  boslcp3 host console logs during 2nd attempt of reboot

** Attachment added: "Second attempt of host reboot_boslcp3"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127933/+files/Secong_attempt_of_reboot_boslcp3.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] 

[Kernel-packages] [Bug 1754492] Re: Dell XPS 15 - Turned off Keyboard backlight turns on after resuming from suspend

[Bob Merhebi]

Thanks. I'll try it this weekend.
Moreover, I'd like to add that when suspended the laptop light remains solid. 
Wouldn't it be more appropriate to have it "beat"?

Also, I am getting a pcierrors during boot among other problems. I
reported them in another bug: https://bugs.launchpad.net/ubuntu-
gnome/+bug/1766327

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

Title:
  Dell XPS 15 - Turned off Keyboard backlight turns on after resuming
  from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the Dell XPS 15 (2017; 9560) the turned off keyboard backlight
  turns back on following a suspend.

  Ubuntu GNOME

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Linux krypton 4.13.0-36-generic #40~16.04.1-Ubuntu SMP
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 2553 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9def3c5c-92fd-4360-a403-30fc2e7e6a96
  InstallationDate: Installed on 2017-08-14 (207 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 007: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) Flash Drive
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 003: ID 0c45:6713 Microdia
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=2149c19b-fca4-49d2-809b-e28952692af2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  Tags:  xenial
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

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

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

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

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

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

** Tags added: bionic

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

Title:
  [SRU][Bionic][Thunderx2] kernel panic when connecting a PLX bridge

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  If a PLX bridge is connected on a ThunderX2 the Linux kernel panics on boot.

  [Fix]
  The following patches upstream fixes this issue.
  204f4afa7ae5 PCI: Remove redundant probes for device reset support
  5b0764cac9f1 PCI: Probe for device reset support during enumeration

  [Test]
  1) Connect a PLX bridge to the root complex
  2) Boot Ubuntu kernel

  [Regression Potential]
  This only impacts ThunderX2.

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

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

[Kernel-packages] [Bug 1767194] [NEW] [SRU][Bionic][Thunderx2] kernel panic when connecting a PLX bridge

[Manoj Iyer]

Public bug reported:

[Impact]
If a PLX bridge is connected on a ThunderX2 the Linux kernel panics on boot.

[Fix]
The following patches upstream fixes this issue.
204f4afa7ae5 PCI: Remove redundant probes for device reset support
5b0764cac9f1 PCI: Probe for device reset support during enumeration

[Test]
1) Connect a PLX bridge to the root complex
2) Boot Ubuntu kernel

[Regression Potential]
This only impacts ThunderX2.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Manoj Iyer (manjo)
 Status: New


** Tags: thunder

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

Title:
  [SRU][Bionic][Thunderx2] kernel panic when connecting a PLX bridge

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  If a PLX bridge is connected on a ThunderX2 the Linux kernel panics on boot.

  [Fix]
  The following patches upstream fixes this issue.
  204f4afa7ae5 PCI: Remove redundant probes for device reset support
  5b0764cac9f1 PCI: Probe for device reset support during enumeration

  [Test]
  1) Connect a PLX bridge to the root complex
  2) Boot Ubuntu kernel

  [Regression Potential]
  This only impacts ThunderX2.

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

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

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

Just to be sure, I logged out of Unity and logged into Gnome 3 and the
results are identical. NO USB audio device works.

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

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

[Bob]

apport information

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

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

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio devices no longer work

[Jeff Lane]

** Summary changed:

- Upgrade to Bionic and USB audio device no longer works
+ Upgrade to Bionic and USB audio devices no longer work

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

I also fired up alsamixer and again, the USB audio device is listed and
accessible but not usable for sound in or out.

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

[Kernel-packages] [Bug 1762844] boslcp3 crashed_used X from xmon prompt

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:22 
EDT---


Attached consolel logs for step(3) & step(4)

** Attachment added: "boslcp3 crashed_used X from xmon prompt"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127892/+files/boslcp3_usedX_xmonprompt.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c 

[Kernel-packages] [Bug 1762844] qla2xxx version 10.00.00.04-k

[bugproxy]

--- Comment (attachment only) From dougm...@us.ibm.com 2018-04-26 10:51 
EDT---


** Attachment added: "qla2xxx version 10.00.00.04-k"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127894/+files/qla2xxx-10.00.00.04-k.tgz

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c 

[Kernel-packages] [Bug 1762844] op-buid instructions for patched skiroot build

[bugproxy]

--- Comment on attachment From mauri...@br.ibm.com 2018-04-26 14:00 
EDT---


Attaching the instructions to build skiroot/skiboot/Petitboot/all with op-build
(in this case, a patched skiroot's kernel -- zImage.epapr),  per Dwip's request.

Hopefully this might help others in the future.

(In reply to comment #203)
> The skiroot kernel build is available at:
>   
> http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/skiroot/bz166588/zImage.
> epapr_4.15.14-openpower1.bz166588c132

** Attachment added: "op-buid instructions for patched skiroot build"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127895/+files/file_166588.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = 

[Kernel-packages] [Bug 1762844] boslcp3_host reboots multiple times

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:24 
EDT---


Attached boslcp3 host console logs for step (5)

** Attachment added: "boslcp3_host reboots multiple times"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127893/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] 

[Kernel-packages] [Bug 1762844] boslcp3g4 xml

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:31 
EDT---


** Attachment added: "boslcp3g4 xml"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127891/+files/boslcp3g4.dumpxml

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1767180/+attachment/5127852/+files/IwConfig.txt

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

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

[Bob]

apport information

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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/1767180/+subscriptions

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

[Kernel-packages] [Bug 1767180] Re: Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work using the Realtek 8822BE driver

[Bob]

apport information

** Tags added: apport-collected staging

** Description changed:

  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work
  
  What happened instead
  Bluetooth does not work
  
  lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters program,
  but on rfkill it is not blocked, and it is not disabled on the
  motherboards' settings.
  
- This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and
- Ubuntu 17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't
- work.
+ This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  azul   1431 F pulseaudio
+  /dev/snd/controlC0:  azul   1431 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-04-08 (18 days ago)
+ InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-20-generic N/A
+  linux-backports-modules-4.15.0-20-generic  N/A
+  linux-firmware 1.173
+ StagingDrivers: r8822be
+ Tags:  bionic staging
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/09/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1301
+ dmi.board.asset.tag: Default string
+ dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx: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

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

** Attachment added: "sound-line-in-input.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127838/+files/sound-line-in-input.png

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug 

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

** Attachment added: "sound-webcam-mic-input.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127839/+files/sound-webcam-mic-input.png

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this 

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

In the previous two screen shots, note that the Settings heading changes
for each output device I choose, EXCEPT for the USB audio output device
(as in this screenshot).

** Attachment added: "sound-Jabra-Speak-output.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127837/+files/sound-Jabra-Speak-output.png

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

** Attachment added: "sound-built-in-digital-output.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127835/+files/sound-built-in-digital-output.png

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage 

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

** Attachment added: "sound-line-out-output.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127836/+files/sound-line-out-output.png

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this 

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

Finally, I plugged a headset into the line-in/out jack on the
motherboard and that does work for both input and output.

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

In these three screen shots, note that the settings ONLY apply to the
line-in device, even when I select the webcam mic and the Jabra Speak,
the only settings options are for line-in.

Both of these devices worked as input devices under Xenial.

** Attachment added: "sound-Jabra-Speak-input.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767181/+attachment/5127840/+files/sound-Jabra-Speak-input.png

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: 

[Kernel-packages] [Bug 1767181] [NEW] Upgrade to Bionic and USB audio device no longer works

[Jeff Lane]

Public bug reported:

I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
for conference calls, hangouts, etc.

Yesterday (and ever since I bought the device) I was able to use this
device for audio output and input on Xenial.

Today, after upgrading to Bionic, I am no longer able to use the device.

Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
[14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
[14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
[14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
[14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
[14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
[14133.075895] usb 3-2.1.4: USB disconnect, device number 5
[14145.362837] usb 3-2.4: USB disconnect, device number 7
[14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
[14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420
[14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
[14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
[14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
[14240.079238] usb 3-2.1.3: USB disconnect, device number 8
[14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
[14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, idProduct=0420
[14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
[14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
[14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

And it appears on the USB bus:
bladernr@galactica:~$ lsusb
Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
However, when I select it, and try a test sound, the output STILL comes out of 
the desktop's line-out and NOT the USB audio device.

Likewise, on the Input tab, if I select the Jabra, no sound is detected
when I speak.

Thinking this might be because I'm using a USB hub, I disconnected the
hub and plugged the device in directly to an onboard USB3 port but the
problem persists.  The device appears as an available output and input
source, but sound does not come out of it (it still comes out the line-
out despite the fact I have selected the USB device) and no sound is
detected when testing the input side.

I also plugged in a USB webcam that has a built in microphone,  LIke the
Jabra Speak 510, my USB webcam Microphone appears as an available input
device and like the Jabra, no sound is detected when I select the webcam
microphone.  USB audio seems to be completely inoperative on Bionic.

Looking at the Sound Settings menu, I notice that the title changes with
each device I choose, however it does NOT change when I choose the USB
devices.  See attached screen shots for more info there.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Apr 26 15:24:56 2018
InstallationDate: Installed on 2016-02-11 (805 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Upgrade to Bionic and USB audio device no longer works

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and 

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

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

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

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

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

** Tags added: bionic

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

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

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and
  Ubuntu 17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't
  work.

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

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

[Kernel-packages] [Bug 1762844] op-buid instructions for patched skiroot build

[bugproxy]

--- Comment on attachment From mauri...@br.ibm.com 2018-04-26 14:00 
EDT---


Attaching the instructions to build skiroot/skiboot/Petitboot/all with op-build
(in this case, a patched skiroot's kernel -- zImage.epapr),  per Dwip's request.

Hopefully this might help others in the future.

(In reply to comment #203)
> The skiroot kernel build is available at:
>   
> http://dorno.rch.stglabs.ibm.com/~mauricfo/kernel/skiroot/bz166588/zImage.
> epapr_4.15.14-openpower1.bz166588c132

** Attachment added: "op-buid instructions for patched skiroot build"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127831/+files/file_166588.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = 

[Kernel-packages] [Bug 1762844] boslcp3_host reboots multiple times

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:24 
EDT---


Attached boslcp3 host console logs for step (5)

** Attachment added: "boslcp3_host reboots multiple times"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127829/+files/boslcp3_rebooting_muliptl_times_with_proper_kernel.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] 

[Kernel-packages] [Bug 1762844] qla2xxx version 10.00.00.04-k

[bugproxy]

--- Comment (attachment only) From dougm...@us.ibm.com 2018-04-26 10:51 
EDT---


** Attachment added: "qla2xxx version 10.00.00.04-k"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127830/+files/qla2xxx-10.00.00.04-k.tgz

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c 

[Kernel-packages] [Bug 1762844] boslcp3g3 xml

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 
EDT---


** Attachment added: "boslcp3g3 xml"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127826/+files/boslcp3g3.dumpxml

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] boslcp3 crashed_used X from xmon prompt

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-26 04:22 
EDT---


Attached consolel logs for step(3) & step(4)

** Attachment added: "boslcp3 crashed_used X from xmon prompt"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127828/+files/boslcp3_usedX_xmonprompt.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c 

[Kernel-packages] [Bug 1762844] boslcp3g4 xml

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:31 
EDT---


** Attachment added: "boslcp3g4 xml"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127827/+files/boslcp3g4.dumpxml

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] sol console log

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-21 17:04 
EDT---


** Attachment added: "sol console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127823/+files/boslcp3.0421.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] dmesg logs from xmon prompt_boslcp3

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-16 01:31 
EDT---


Attached dl logs from xmon pormpt _boslcp3

** Attachment added: "dmesg logs from xmon prompt_boslcp3"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127820/+files/dmesg_xmon_boslcp3.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  

[Kernel-packages] [Bug 1762844] boslcp3g1 xml

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-24 09:30 
EDT---


** Attachment added: "boslcp3g1 xml"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127825/+files/boslcp3g1.dumpxml

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] dmesg output 0418

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-18 12:01 
EDT---


** Attachment added: "dmesg output 0418"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127821/+files/dmesg.201804181042

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] Host console log

[bugproxy]

--- Comment on attachment From chngu...@us.ibm.com 2018-04-13 17:17 
EDT---


The full log of the Host during couple reboot, start test on guest then system 
drop into xmon.

** Attachment added: "Host console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127819/+files/boslcp3.0413.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c 

[Kernel-packages] [Bug 1762844] console log

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-20 20:08 
EDT---


** Attachment added: "console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5127822/+files/boslcp3.0420.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

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

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

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

[hitausmomentti]

apport information

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

Title:
  Bionic: ALPS GlidePoint uses wrong driver, works badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ALPS GlidePoint trackpad on my HP EliteBook 1030 G1 no longer
  works properly on Ubuntu Bionic.

  A similar problem happened with the previous Ubuntu release, but I was
  able to work around it. On both Bionic and Artful, both the hid_alps
  and the psmouse drivers get loaded by default and xinput shows a
  trackpad from both drivers.

  As long as the psmouse driver is loaded, synclient appears to work
  happily, but doesn't do anything and actually only the other driver
  does anything. Xinput and the Xorg logs show the trackpad twice.

  On Artful, forcing psmouse to be the only driver made everything,
  including all the settings available in synaptics tooling work
  perfectly. Now only the hid_alps driver seems to even make the pointer
  move, and there don't seem to be any ways to configure it much at all,
  for instance the speed is barely fast enough to be usable.

  Based on synclient only working with it and the lack of errors in any
  logs that I could think of, psmouse still seems the correct driver. It
  just doesn't make the pointer move any more. I tried installing some
  xserver-xorg-input packages that I didn't have installed, but it made
  the hid_alps driver work worse.

  I was not able to get the old behavior back just by booting the old
  kernel.

  xinput ():
  $ xinput 
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ATML1000:00 03EB:8A76 id=10   [slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=16   [slave  pointer  (2)]
  ⎜   ↳ ALP000E:00 044E:120C  id=12   [slave  pointer  (2)] 
# hid_alps
  ⎜   ↳ AlpsPS/2 ALPS GlidePoint  id=15   [slave  pointer  (2)] 
# psmouse
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)] 

  
  ↳ Sleep Button  id=8[slave  keyboard (3)] 

  
  ↳ HP HD Camera: HP HD Cameraid=9[slave  keyboard (3)] 

  
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)] 

  
  ↳ HP Wireless hotkeys   id=13   [slave  keyboard (3)]
  ↳ HP WMI hotkeysid=14   [slave  keyboard (3)]
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lauri 12637 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-18 (190 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: HP HP EliteBook 1030 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0ebbe8b4-a902-49f3-bf6b-7371bc38e0e6 ro noquiet nosplash 
intel_iommu=on cgroup_enable=memory swapaccount=1 spectre_v2=off nopti
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev pulse pulse-access 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N86 Ver. 01.04
  dmi.board.name: 80FB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.35
  dmi.chassis.asset.tag: 5CG64958MS
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN86Ver.01.04:bd08/09/2016:svnHP:pnHPEliteBook1030G1:pvr:rvnHP:rn80FB:rvrKBCVersion14.35:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  

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

[hitausmomentti]

apport information

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

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

Title:
  Bionic: ALPS GlidePoint uses wrong driver, works badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ALPS GlidePoint trackpad on my HP EliteBook 1030 G1 no longer
  works properly on Ubuntu Bionic.

  A similar problem happened with the previous Ubuntu release, but I was
  able to work around it. On both Bionic and Artful, both the hid_alps
  and the psmouse drivers get loaded by default and xinput shows a
  trackpad from both drivers.

  As long as the psmouse driver is loaded, synclient appears to work
  happily, but doesn't do anything and actually only the other driver
  does anything. Xinput and the Xorg logs show the trackpad twice.

  On Artful, forcing psmouse to be the only driver made everything,
  including all the settings available in synaptics tooling work
  perfectly. Now only the hid_alps driver seems to even make the pointer
  move, and there don't seem to be any ways to configure it much at all,
  for instance the speed is barely fast enough to be usable.

  Based on synclient only working with it and the lack of errors in any
  logs that I could think of, psmouse still seems the correct driver. It
  just doesn't make the pointer move any more. I tried installing some
  xserver-xorg-input packages that I didn't have installed, but it made
  the hid_alps driver work worse.

  I was not able to get the old behavior back just by booting the old
  kernel.

  xinput ():
  $ xinput 
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ATML1000:00 03EB:8A76 id=10   [slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=16   [slave  pointer  (2)]
  ⎜   ↳ ALP000E:00 044E:120C  id=12   [slave  pointer  (2)] 
# hid_alps
  ⎜   ↳ AlpsPS/2 ALPS GlidePoint  id=15   [slave  pointer  (2)] 
# psmouse
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)] 

  
  ↳ Sleep Button  id=8[slave  keyboard (3)] 

  
  ↳ HP HD Camera: HP HD Cameraid=9[slave  keyboard (3)] 

  
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)] 

  
  ↳ HP Wireless hotkeys   id=13   [slave  keyboard (3)]
  ↳ HP WMI hotkeysid=14   [slave  keyboard (3)]
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lauri 12637 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-18 (190 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: HP HP EliteBook 1030 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0ebbe8b4-a902-49f3-bf6b-7371bc38e0e6 ro noquiet nosplash 
intel_iommu=on cgroup_enable=memory swapaccount=1 spectre_v2=off nopti
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev pulse pulse-access 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N86 Ver. 01.04
  dmi.board.name: 80FB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.35
  dmi.chassis.asset.tag: 5CG64958MS
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN86Ver.01.04:bd08/09/2016:svnHP:pnHPEliteBook1030G1:pvr:rvnHP:rn80FB:rvrKBCVersion14.35:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  

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

[hitausmomentti]

apport information

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

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

Title:
  Bionic: ALPS GlidePoint uses wrong driver, works badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ALPS GlidePoint trackpad on my HP EliteBook 1030 G1 no longer
  works properly on Ubuntu Bionic.

  A similar problem happened with the previous Ubuntu release, but I was
  able to work around it. On both Bionic and Artful, both the hid_alps
  and the psmouse drivers get loaded by default and xinput shows a
  trackpad from both drivers.

  As long as the psmouse driver is loaded, synclient appears to work
  happily, but doesn't do anything and actually only the other driver
  does anything. Xinput and the Xorg logs show the trackpad twice.

  On Artful, forcing psmouse to be the only driver made everything,
  including all the settings available in synaptics tooling work
  perfectly. Now only the hid_alps driver seems to even make the pointer
  move, and there don't seem to be any ways to configure it much at all,
  for instance the speed is barely fast enough to be usable.

  Based on synclient only working with it and the lack of errors in any
  logs that I could think of, psmouse still seems the correct driver. It
  just doesn't make the pointer move any more. I tried installing some
  xserver-xorg-input packages that I didn't have installed, but it made
  the hid_alps driver work worse.

  I was not able to get the old behavior back just by booting the old
  kernel.

  xinput ():
  $ xinput 
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ATML1000:00 03EB:8A76 id=10   [slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=16   [slave  pointer  (2)]
  ⎜   ↳ ALP000E:00 044E:120C  id=12   [slave  pointer  (2)] 
# hid_alps
  ⎜   ↳ AlpsPS/2 ALPS GlidePoint  id=15   [slave  pointer  (2)] 
# psmouse
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)] 

  
  ↳ Sleep Button  id=8[slave  keyboard (3)] 

  
  ↳ HP HD Camera: HP HD Cameraid=9[slave  keyboard (3)] 

  
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)] 

  
  ↳ HP Wireless hotkeys   id=13   [slave  keyboard (3)]
  ↳ HP WMI hotkeysid=14   [slave  keyboard (3)]
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lauri 12637 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-18 (190 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: HP HP EliteBook 1030 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0ebbe8b4-a902-49f3-bf6b-7371bc38e0e6 ro noquiet nosplash 
intel_iommu=on cgroup_enable=memory swapaccount=1 spectre_v2=off nopti
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev pulse pulse-access 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N86 Ver. 01.04
  dmi.board.name: 80FB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.35
  dmi.chassis.asset.tag: 5CG64958MS
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN86Ver.01.04:bd08/09/2016:svnHP:pnHPEliteBook1030G1:pvr:rvnHP:rn80FB:rvrKBCVersion14.35:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  

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

[hitausmomentti]

apport information

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

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

Title:
  Bionic: ALPS GlidePoint uses wrong driver, works badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ALPS GlidePoint trackpad on my HP EliteBook 1030 G1 no longer
  works properly on Ubuntu Bionic.

  A similar problem happened with the previous Ubuntu release, but I was
  able to work around it. On both Bionic and Artful, both the hid_alps
  and the psmouse drivers get loaded by default and xinput shows a
  trackpad from both drivers.

  As long as the psmouse driver is loaded, synclient appears to work
  happily, but doesn't do anything and actually only the other driver
  does anything. Xinput and the Xorg logs show the trackpad twice.

  On Artful, forcing psmouse to be the only driver made everything,
  including all the settings available in synaptics tooling work
  perfectly. Now only the hid_alps driver seems to even make the pointer
  move, and there don't seem to be any ways to configure it much at all,
  for instance the speed is barely fast enough to be usable.

  Based on synclient only working with it and the lack of errors in any
  logs that I could think of, psmouse still seems the correct driver. It
  just doesn't make the pointer move any more. I tried installing some
  xserver-xorg-input packages that I didn't have installed, but it made
  the hid_alps driver work worse.

  I was not able to get the old behavior back just by booting the old
  kernel.

  xinput ():
  $ xinput 
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ATML1000:00 03EB:8A76 id=10   [slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=16   [slave  pointer  (2)]
  ⎜   ↳ ALP000E:00 044E:120C  id=12   [slave  pointer  (2)] 
# hid_alps
  ⎜   ↳ AlpsPS/2 ALPS GlidePoint  id=15   [slave  pointer  (2)] 
# psmouse
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)] 

  
  ↳ Sleep Button  id=8[slave  keyboard (3)] 

  
  ↳ HP HD Camera: HP HD Cameraid=9[slave  keyboard (3)] 

  
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)] 

  
  ↳ HP Wireless hotkeys   id=13   [slave  keyboard (3)]
  ↳ HP WMI hotkeysid=14   [slave  keyboard (3)]
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lauri 12637 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-18 (190 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: HP HP EliteBook 1030 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0ebbe8b4-a902-49f3-bf6b-7371bc38e0e6 ro noquiet nosplash 
intel_iommu=on cgroup_enable=memory swapaccount=1 spectre_v2=off nopti
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev pulse pulse-access 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N86 Ver. 01.04
  dmi.board.name: 80FB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.35
  dmi.chassis.asset.tag: 5CG64958MS
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN86Ver.01.04:bd08/09/2016:svnHP:pnHPEliteBook1030G1:pvr:rvnHP:rn80FB:rvrKBCVersion14.35:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  

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

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

Title:
  Linux 4.15 network LAN not resumed after sleeping

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux 4.15.0-15: network LAN not resumed after sleeping on
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller.

  On 4.13 it's worked correctly.

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

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

[Kernel-packages] [Bug 1767178] Re: Bionic: ALPS GlidePoint uses wrong driver, works badly

[hitausmomentti]

turns out I had'nt removed all  the old xorg settings that were
necessary before. removing a few leftover lines in xorg.conf.d seems to
have fixed the problem

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

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

Title:
  Bionic: ALPS GlidePoint uses wrong driver, works badly

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The ALPS GlidePoint trackpad on my HP EliteBook 1030 G1 no longer
  works properly on Ubuntu Bionic.

  A similar problem happened with the previous Ubuntu release, but I was
  able to work around it. On both Bionic and Artful, both the hid_alps
  and the psmouse drivers get loaded by default and xinput shows a
  trackpad from both drivers.

  As long as the psmouse driver is loaded, synclient appears to work
  happily, but doesn't do anything and actually only the other driver
  does anything. Xinput and the Xorg logs show the trackpad twice.

  On Artful, forcing psmouse to be the only driver made everything,
  including all the settings available in synaptics tooling work
  perfectly. Now only the hid_alps driver seems to even make the pointer
  move, and there don't seem to be any ways to configure it much at all,
  for instance the speed is barely fast enough to be usable.

  Based on synclient only working with it and the lack of errors in any
  logs that I could think of, psmouse still seems the correct driver. It
  just doesn't make the pointer move any more. I tried installing some
  xserver-xorg-input packages that I didn't have installed, but it made
  the hid_alps driver work worse.

  I was not able to get the old behavior back just by booting the old
  kernel.

  xinput ():
  $ xinput 
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ATML1000:00 03EB:8A76 id=10   [slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=16   [slave  pointer  (2)]
  ⎜   ↳ ALP000E:00 044E:120C  id=12   [slave  pointer  (2)] 
# hid_alps
  ⎜   ↳ AlpsPS/2 ALPS GlidePoint  id=15   [slave  pointer  (2)] 
# psmouse
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)] 

  
  ↳ Sleep Button  id=8[slave  keyboard (3)] 

  
  ↳ HP HD Camera: HP HD Cameraid=9[slave  keyboard (3)] 

  
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)] 

  
  ↳ HP Wireless hotkeys   id=13   [slave  keyboard (3)]
  ↳ HP WMI hotkeysid=14   [slave  keyboard (3)]
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lauri 12637 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-18 (190 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: HP HP EliteBook 1030 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0ebbe8b4-a902-49f3-bf6b-7371bc38e0e6 ro noquiet nosplash 
intel_iommu=on cgroup_enable=memory swapaccount=1 spectre_v2=off nopti
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev pulse pulse-access 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N86 Ver. 01.04
  dmi.board.name: 80FB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.35
  dmi.chassis.asset.tag: 5CG64958MS
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 

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

Title:
  Bionic: ALPS GlidePoint uses wrong driver, works badly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ALPS GlidePoint trackpad on my HP EliteBook 1030 G1 no longer
  works properly on Ubuntu Bionic.

  A similar problem happened with the previous Ubuntu release, but I was
  able to work around it. On both Bionic and Artful, both the hid_alps
  and the psmouse drivers get loaded by default and xinput shows a
  trackpad from both drivers.

  As long as the psmouse driver is loaded, synclient appears to work
  happily, but doesn't do anything and actually only the other driver
  does anything. Xinput and the Xorg logs show the trackpad twice.

  On Artful, forcing psmouse to be the only driver made everything,
  including all the settings available in synaptics tooling work
  perfectly. Now only the hid_alps driver seems to even make the pointer
  move, and there don't seem to be any ways to configure it much at all,
  for instance the speed is barely fast enough to be usable.

  Based on synclient only working with it and the lack of errors in any
  logs that I could think of, psmouse still seems the correct driver. It
  just doesn't make the pointer move any more. I tried installing some
  xserver-xorg-input packages that I didn't have installed, but it made
  the hid_alps driver work worse.

  I was not able to get the old behavior back just by booting the old
  kernel.

  xinput ():
  $ xinput 
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ATML1000:00 03EB:8A76 id=10   [slave  pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouseid=16   [slave  pointer  (2)]
  ⎜   ↳ ALP000E:00 044E:120C  id=12   [slave  pointer  (2)] 
# hid_alps
  ⎜   ↳ AlpsPS/2 ALPS GlidePoint  id=15   [slave  pointer  (2)] 
# psmouse
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)] 

  
  ↳ Sleep Button  id=8[slave  keyboard (3)] 

  
  ↳ HP HD Camera: HP HD Cameraid=9[slave  keyboard (3)] 

  
  ↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)] 

  
  ↳ HP Wireless hotkeys   id=13   [slave  keyboard (3)]
  ↳ HP WMI hotkeysid=14   [slave  keyboard (3)]
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lauri 12637 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-18 (190 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: HP HP EliteBook 1030 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0ebbe8b4-a902-49f3-bf6b-7371bc38e0e6 ro noquiet nosplash 
intel_iommu=on cgroup_enable=memory swapaccount=1 spectre_v2=off nopti
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev pulse pulse-access 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/09/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N86 Ver. 01.04
  dmi.board.name: 80FB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.35
  dmi.chassis.asset.tag: 5CG64958MS
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN86Ver.01.04:bd08/09/2016:svnHP:pnHPEliteBook1030G1:pvr:rvnHP:rn80FB:rvrKBCVersion14.35:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 1030 G1