[Kernel-packages] [Bug 1775391] Re: kernel: Fix arch random implementation

[Frank Heimes]

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

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

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

Title:
  kernel: Fix arch random implementation

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM reports that arch_get_random_seed_long() invocations may slow down the
  interrupt handling on heavy interrupt producing loads.

  The existing random device driver calls arch_get_random_seed_long() in
  interrupt context. The current implementation of this function uses the
  PRNO(TRNG) instruction to provide good entropy. This instruction is
  relatively slow and expensive and may slow down the capacity of interrupts 
which can be handled per cpu.

  This fix reworks the arch_get_random_seed implementation.  It introduces a
  buffer concept to decouple the delivery of random data via
  arch_get_random_seed*() from the generation of new random bytes and so
  does not limit the interrupt handling per cpu any more.

  == Fix ==
  966f53e750ae ("s390/archrandom: Rework arch random implementation.")

  == Regression Potential ==
  Low.  This fix is limited to s390.

  == Test Case ==
  Verified upfront by IBM during upstream integration



  Description:  kernel: Fix arch random implementation
  Symptom:  arch_get_random_seed_long() invocations may slow down the
    interrupt handling on heavy interrupt producing loads.
  Problem:  The existing random device driver calls
    arch_get_random_seed_long() in interrupt context. The
    current implementation of this function uses the
    PRNO(TRNG) instruction to provide good entropy. This
    instruction is relatively slow and expensive and may
    slow down the capacity of interrupts which can be handled
    per cpu.
  Solution: This fix reworks the arch_get_random_seed implementation.
    It introduces a buffer concept to decouple the delivery
    of random data via arch_get_random_seed*() from the
    generation of new random bytes and so does not limit
    the interrupt handling per cpu any more.
  Reproduction: Systems with heavy irq load show performance decrease.
  Component:kernel

  Upstream commit(s): kernel 4.18
  966f53e750aedc5f59f9ccae6bbfb8f671c7c842

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

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

[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.

[Frank Heimes]

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

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

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

Title:
  kernel: Fix memory leak on CCA and EP11 CPRB processing.

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Description:  kernel: Fix memory leak on CCA and EP11 CPRB processing.
  Symptom:  Kernel memory not freed when CCA or EP11 CPRB processing fails.
  Problem:  kfree() in code error path missing.
  Solution: Slight rework of the malloc and free places.
  Reproduction: Run application which sends CCA or EP11 crypto requests
    to the crypto card(s). Now switch the cards offline with
    the help of chzcrypt. Monitor top or free output.

  Upstream commit(s): kernel 4.18
  89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21

  == Fix ==
  89a0c0ec0d2e ("s390/zcrypt: Fix CCA and EP11 CPRB processing failure memory 
leak.")

  == Regression Potential ==
  Low.  Limited to s390.

  == Test Case ==
  Verified upfront by IBM during upstream integration.

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

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

[Kernel-packages] [Bug 1777744] Re: 4.15.0-23-generic fails to PXE boot on PPC64

[Lee Trager]

Unable to run apport-collect as the error occurs while PXE booting the
kernel. A panic happens while loading the initrd and a shell is not
available.

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

Title:
  4.15.0-23-generic fails to PXE boot on PPC64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The MAAS CI has a PPC64 machine which is failing to boot into the
  ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic
  from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded.

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

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

[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error

[Patrick Storms]

I have decided to try to eliminate some things.   I ended up formatting
my RAID drives and cleared that out.   I also rebuilt the RAID Array in
hopes of clearing up this issue.  But these did not fix what we are
seeing here.

As to your request regarding selecting versions from the GRUB menu, I
tried the two versions of the kernel that I have installed on this
server.

The two kernels are:
4.15.0-20-generic
4.15.0-23-generic

This is an interesting development.   When I booted the earlier version
(4.15.0-20), I do not get any errors.   I tested several large copies to
a USB drive with no issues.  6 Times I tried to create the issue, but
was not successful.   When I booted back to the new version(4.15.0-23),
it errors almost immediately.   When I went and rebooted back to
4.15.0-20 it errored as well.   So the issue is systemic in both
releases.

I will try the updated kernel next.

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

Title:
  Ubuntu Server 18.04 LTS aacraid error

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

Bug description:
  I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and
  am now running into these raid adapter driver errors.   The server ran
  fine in older version.  My apologies as I lost the exact version, but
  it never had any errors like this version.

  Now when ever I try to copy files to the RAID 5 drive, or untar a
  file, I get these errors now after a few MB's of written data.

  Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  batboat:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I have tried the IRQ debugging tips to no avail.   I loaded in
  Debian9.4.0 and it only briefly showed this error once.   But appears
  to be much more resilient and appears to work fine.


  Jun 19 00:02:21 batboat kernel: [  498.770839] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.139167] aacraid: Host adapter reset 
request. SCSI hang ?
  Jun 19 00:02:37 batboat kernel: [  514.795083] aacraid :03:09.0: Adapter 
health - 199
  Jun 19 00:02:37 batboat kernel: [  514.800376] aacraid :03:09.0: 
outstanding cmd: midlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800378] aacraid :03:09.0: 
outstanding cmd: lowlevel-0
  Jun 19 00:02:37 batboat kernel: [  514.800381] aacraid :03:09.0: 
outstanding cmd: error handler-0
  Jun 19 00:02:37 batboat kernel: [  514.800383] aacraid :03:09.0: 
outstanding cmd: firmware-5
  Jun 19 00:02:37 batboat kernel: [  514.800385] aacraid :03:09.0: 
outstanding cmd: kernel-0
  Jun 19 00:02:37 batboat kernel: [  514.800391] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800394] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800396] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800399] sd 4:0:0:0: Device offlined - 
not ready after error recovery
  Jun 19 00:02:37 batboat kernel: [  514.800401] sd 4:0:0:0: Device offlined - 
not ready after error recovery

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

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

[Kernel-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

[Sujith Pandel]

Update:
I was under the assumption that kvm/kvm_amd module was the suspect.
But I was wrong.
Reason - I tried performing '#modprobe -r kvm_amd kvm' before issuing 
'#systemctl reboot' in the reboot script and the system still halted with 
Ubuntu 18.04 kernel.

@jsalisbury -
I will keep it today and update you by tomorrow.

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

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

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

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

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

[Kernel-packages] [Bug 1734242] Re: Intel 9260/9462/9560 driver support

[guodi]

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

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

Title:
  Intel 9260/9462/9560 driver support

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  Some new 9260/9462/9560 module doesn't work on artful kernel(v4.13) and 
require some commits
  They are
  https://marc.info/?l=linux-wireless=151076478931107=2
  https://marc.info/?l=linux-wireless=151082205418762=2
  https://marc.info/?l=linux-wireless=151082213518769=2

  Those commits have not been merged into iwlwifi-next yet

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

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

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Carl Reinke]

cbf4b38 does NOT have the bug.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  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.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1765683] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000070

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0070

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hard to forcefully reboot ubuntu after starting it up.
  No clue what caused this.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  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:  gdm1139 F pulseaudio
hicham 1716 F pulseaudio
   /dev/snd/controlC0:  gdm1139 F pulseaudio
hicham 1716 F pulseaudio
  Date: Fri Apr 20 13:31:11 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: _nv002366kms+0x5e/0x100 [nvidia_modeset] RSP: 9a7cc312fd00
  Failure: oops
  InstallationDate: Installed on 2018-04-18 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=d5f38b3a-0e58-474f-9b1f-f0c6a3e1a509 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
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0070
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.30
  dmi.board.name: Z170 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.30:bd11/24/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1764752] Re: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0]

[Launchpad Bug Tracker]

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

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

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

Title:
  watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0]

Status in linux package in Ubuntu:
  Expired

Bug description:
  my system often hangs, and can not be done anything

  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
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zellkristian   1649 F pulseaudio
   /dev/snd/controlC0:  zellkristian   1649 F pulseaudio
  Date: Tue Apr 17 00:51:45 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-11 (5 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180410)
  MachineType: Quanta TW9/SW9
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=45e8aaf2-1d42-475b-bce6-df2af413f1a3 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: Q3C24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: US
  dmi.modalias: 
dmi:bvnINSYDE:bvrQ3C24:bd12/24/2009:svnQuanta:pnTW9/SW9:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrUS:
  dmi.product.family: Intel_Mobile
  dmi.product.name: TW9/SW9
  dmi.product.version: 05
  dmi.sys.vendor: Quanta

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

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

[Kernel-packages] [Bug 1764859] Re: BUG: scheduling while atomic: Media/11726/0x00000002

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG: scheduling while atomic: Media/11726/0x0002

Status in linux package in Ubuntu:
  Expired

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Tue Apr 17 22:12:39 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (46 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ 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
  Title: BUG: scheduling while atomic: Media/11726/0x0002
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1765782] Re: general protection fault: 0000 [#1] SMP PTI

[Launchpad Bug Tracker]

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

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

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

Title:
  general protection fault:  [#1] SMP PTI

Status in linux package in Ubuntu:
  Expired

Bug description:
  ubuntu 18.04

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-17-generic 4.15.0-17.18
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-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:  gdm2254 F pulseaudio
norin  2750 F pulseaudio
   /dev/snd/controlC0:  gdm2254 F pulseaudio
norin  2750 F pulseaudio
  Date: Fri Apr 20 23:25:02 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=3bc7942c-e47d-4ab6-88d0-60e516b5b445
  InstallationDate: Installed on 2018-04-12 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  MachineType: Acer Aspire VN7-591G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic.efi.signed 
root=UUID=ab857ae8-8c35-408a-afab-b0ed8eb0303d ro
  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
  Title: general protection fault:  [#1] SMP PTI
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-591G
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.15:bd08/06/2015:svnAcer:pnAspireVN7-591G:pvrV1.15:rvnAcer:rnAspireVN7-591G:rvrV1.15:cvnAcer:ct10:cvrV1.15:
  dmi.product.family: HSW
  dmi.product.name: Aspire VN7-591G
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1765822] Re: BUG: Bad page map in process Compositor pte:200000000000 pmd:1c6dc78067

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG: Bad page map in process Compositor  pte:2000
  pmd:1c6dc78067

Status in linux package in Ubuntu:
  Expired

Bug description:
  This showed up after Chrome started crashing.

  Ubuntu 4.15.0-15.16-generic 4.15.15

  This is a fresh "Erase disk and reinstall" of minimal from yesterdays
  bionic iso

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Fri Apr 20 12:07:09 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-19 (0 days ago)
  InstallationMedia:
   
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=d9b05c55-71bb-4f4f-bdfd-43dd79de4c1d ro reboot=pci pcie_aspm=off
  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
  Title: BUG: Bad page map in process Compositor  pte:2000 
pmd:1c6dc78067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH EXTREME
  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.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME: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/1765822/+subscriptions

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

[Kernel-packages] [Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04

[Daniel van Vugt]

Your logs also show you have "nvidia-modeset" being loaded still. So,
now that you have installed the official driver, maybe also try undoing
the changes from comment #26.

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

Title:
  [nvidia] GDM no longer presents GUI login Ubuntu 18.04

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Background:

  Did a clean install of Ubuntu 18.04, standard Gnome desktop. Used
  nVidia proprietary drivers from Ubuntu repo. Worked quite well for
  over two weeks. When booting up on Friday 15th June, 2018 no longer
  had a GUI login screen. There was just a few lines in tty1. Can still
  login to other terminals and through SSH.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 17 22:53:22 2018
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-31T00:51:08.204556
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.2-0ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777378/+subscriptions

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

[Kernel-packages] [Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04

[Daniel van Vugt]

Please also attach: /usr/share/X11/xorg.conf.d/10-nvidia.conf
in case it is relevant.

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

Title:
  [nvidia] GDM no longer presents GUI login Ubuntu 18.04

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Background:

  Did a clean install of Ubuntu 18.04, standard Gnome desktop. Used
  nVidia proprietary drivers from Ubuntu repo. Worked quite well for
  over two weeks. When booting up on Friday 15th June, 2018 no longer
  had a GUI login screen. There was just a few lines in tty1. Can still
  login to other terminals and through SSH.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 17 22:53:22 2018
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-31T00:51:08.204556
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.2-0ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777378/+subscriptions

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

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[viny]

Facing the same problem here... Dell inspiron 7000.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10HX.M034.20110426.SSH:bd04/26/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr10HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr10HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: RF511/RF411/RF711
  

[Kernel-packages] [Bug 1774606] Re: [Redpine] Wifi AP does not work

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [Redpine] Wifi AP does not work

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver
  for 4.15 kernel.

  Several issues were observed in Redpine driver which supports RS9113 Wifi+BT 
combo chip:
  1. 40Mhz connection issue
  2. Mode 1,13,14,4,6 change issue
  3. SoftAP failure issue

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

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

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

[Kernel-packages] [Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04

[Daniel van Vugt]

Other than the aforementioned hardware experimentation, you might also
want to try downgrading the kernel. Older kernels are likely still
installed on your machine so all you need is to get to the grub menu
(which can be difficult) and choose an older kernel at boot time.

See: https://askubuntu.com/questions/16042/how-to-get-to-the-grub-menu-
at-boot-time

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

Title:
  [nvidia] GDM no longer presents GUI login Ubuntu 18.04

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Background:

  Did a clean install of Ubuntu 18.04, standard Gnome desktop. Used
  nVidia proprietary drivers from Ubuntu repo. Worked quite well for
  over two weeks. When booting up on Friday 15th June, 2018 no longer
  had a GUI login screen. There was just a few lines in tty1. Can still
  login to other terminals and through SSH.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 17 22:53:22 2018
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-31T00:51:08.204556
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.2-0ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777378/+subscriptions

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

[Kernel-packages] [Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04

[Daniel van Vugt]

Thanks for searching.

It appears this is now a problem in the nvidia driver only, if not a
hardware/cable problem. So reassigning...

** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)

** No longer affects: mutter (Ubuntu)

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

Title:
  [nvidia] GDM no longer presents GUI login Ubuntu 18.04

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Background:

  Did a clean install of Ubuntu 18.04, standard Gnome desktop. Used
  nVidia proprietary drivers from Ubuntu repo. Worked quite well for
  over two weeks. When booting up on Friday 15th June, 2018 no longer
  had a GUI login screen. There was just a few lines in tty1. Can still
  login to other terminals and through SSH.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 17 22:53:22 2018
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-31T00:51:08.204556
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.2-0ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-20 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777378/+subscriptions

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

[Kernel-packages] [Bug 1777378] [NEW] [nvidia] GDM no longer presents GUI login Ubuntu 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Background:

Did a clean install of Ubuntu 18.04, standard Gnome desktop. Used nVidia
proprietary drivers from Ubuntu repo. Worked quite well for over two
weeks. When booting up on Friday 15th June, 2018 no longer had a GUI
login screen. There was just a few lines in tty1. Can still login to
other terminals and through SSH.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jun 17 22:53:22 2018
InstallationDate: Installed on 2018-05-20 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2018-05-31T00:51:08.204556
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-20 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NonfreeKernelModules: nvidia_modeset nvidia
Package: gdm3 3.28.2-0ubuntu1.2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Tags:  bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-20 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NonfreeKernelModules: nvidia_modeset nvidia
Package: mutter
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Tags:  bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True
mtime.conffile..etc.gdm3.custom.conf: 2018-06-18T00:27:55.234654

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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


** Tags: amd64 apport-bug apport-collected bionic nvidia
-- 
[nvidia] GDM no longer presents GUI login Ubuntu 18.04
https://bugs.launchpad.net/bugs/1777378
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.

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

[Kernel-packages] [Bug 1748853] Re: Intel 9462 A370:42A4 doesn't work

[AceLan Kao]

guodi, could you paste your wifi dev id and subsystem id here?
You can find it by "lspci -nnk", just the id like this [8086:A370][8086:42A4]

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

Title:
  Intel 9462 A370:42A4 doesn't work

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The PCI ID [A370:42A4] is not included in iwlwifi driver, so that Intel 9462 
with that ID won't work.

  [Fix]
  According the 2 patches sent to 4.15 stable, which were not be included 
before 4.15 EOL, so we cherry pick the 2 patches to Ubuntu 4.15 kernel.
  https://www.spinics.net/lists/stable/msg235420.html

  [Regression Potential]
  Adding IDs, no regression could be happened

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

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

[Kernel-packages] [Bug 1772610] Re: Adding back alx WoL feature

[AceLan Kao]

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Adding back alx WoL feature

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

Bug description:
  [Impact]
  The WoL feature is a must to pass Energy Star 6.1 and above.
  The power consumption will be measured during S3 with WoL is enabled.

  [Test case]
  Verified pass on new Dell machines without the wake up issue.

  [Regression potential]
  No regression.
  We disable this feature by default, so the driver behavior will be the same. 
We'll leave this feature disabled by default before we can fix the 
unintentional wake up issue.

  [Misc]
  Upstream maintainer insists to fix the wake up issue before we can add this 
feature back to the driver, so make the patch stay in Ubuntu kernel only. We'll 
verify WoL on every new machines and try to fix this issue when we encounter it.

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

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

[Kernel-packages] [Bug 1777658] Re: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build

[Daniel van Vugt]

We seem to be missing the aforementioned make.log.

Can you please find it (under /var/lib/dkms or similar) and attach it
here?

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

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

Title:
  nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Tried to watch world cup stream - DKMS module failed in browser.
  Perhpas this has to do with some sort of DRM demuxing that the
  graphics card is responsible for?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-dkms-390 390.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for nvidia-390.48 for kernel 4.15.0-23-generic (x86_64)
   Tue Jun 19 10:14:54 EDT 2018
   make: *** No rule to make target 'modules'.  Stop.
  DKMSKernelVersion: 4.15.0-23-generic
  Date: Tue Jun 19 10:14:54 2018
  InstallationDate: Installed on 2018-03-22 (89 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  PackageVersion: 390.48-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-dkms-390 390.48-0ubuntu3: nvidia kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777658/+subscriptions

-- 
Mailing list: https://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 1777204] package linux-image-4.15.0-23-lowlatency (not installed) failed to install/upgrade: installed linux-image-4.15.0-23-lowlatency package pre-removal script subprocess

[Mustafa Kocaturk]

Thanks for responding. I think this report was triggered by a new linux image 
installation failing because of lack of space in the /boot partition.
A re-install, using aptitude, after removing old kernels, had already resolved 
the issue before submitting the report.
The report was auto generated after a reboot. I filled and it as appropriate, 
then realized it was a duplicate.
It is a non-bug as such and may be closed :).

Best regards,
Mustafa
  
> On Jun 19, 2018, at 9:09 AM, Joseph Salisbury 
>  wrote:
> 
> You may need to run the following from a terminal:
> 
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get update
> 
> Then re-install the package or updates.
> 
> If that does not resolve your issue, please mark the bug as "Confirmed"
> 
> ** Changed in: linux (Ubuntu)
>   Importance: Undecided => Low
> 
> ** Changed in: linux (Ubuntu)
>   Status: Confirmed => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1777204
> 
> Title:
>  package linux-image-4.15.0-23-lowlatency (not installed) failed to
>  install/upgrade: installed linux-image-4.15.0-23-lowlatency package
>  pre-removal script subprocess returned error exit status 1
> 
> Status in linux package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Known bug, worked around by removing old kernels.
> 
>  ProblemType: Package
>  DistroRelease: Ubuntu 18.10
>  Package: linux-image-4.15.0-23-lowlatency (not installed)
>  ProcVersionSignature: Ubuntu 4.15.0-24.26-lowlatency 4.15.18
>  Uname: Linux 4.15.0-24-lowlatency x86_64
>  ApportVersion: 2.20.10-0ubuntu3
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  gdm2193 F pulseaudio
>mlthost2767 F pulseaudio
>  Date: Fri Jun 15 19:32:44 2018
>  ErrorMessage: installed linux-image-4.15.0-23-lowlatency package pre-removal 
> script subprocess returned error exit status 1
>  HibernationDevice: RESUME=UUID=8fe6b1c9-1cbd-491d-b1fb-28cb0310bbe4
>  InstallationDate: Installed on 2017-07-18 (332 days ago)
>  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
> (20170215.2)
>  Lsusb:
>   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
>   Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. 
>   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  MachineType: Dell Inc. OptiPlex 5050
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-lowlatency 
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
>  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
> PulseAudio daemon running, or not running as session daemon.
>  Python3Details: /usr/bin/python3.6, Python 3.6.6rc1, python3-minimal, 3.6.5-3
>  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
>  RelatedPackageVersions: grub-pc 2.02-2ubuntu10
>  SourcePackage: linux
>  Title: package linux-image-4.15.0-23-lowlatency (not installed) failed to 
> install/upgrade: installed linux-image-4.15.0-23-lowlatency package 
> pre-removal script subprocess returned error exit status 1
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 05/06/2017
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: 1.3.11
>  dmi.board.name: 0782GW
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: A00
>  dmi.chassis.type: 3
>  dmi.chassis.vendor: Dell Inc.
>  dmi.modalias: 
> dmi:bvnDellInc.:bvr1.3.11:bd05/06/2017:svnDellInc.:pnOptiPlex5050:pvr:rvnDellInc.:rn0782GW:rvrA00:cvnDellInc.:ct3:cvr:
>  dmi.product.family: OptiPlex
>  dmi.product.name: OptiPlex 5050
>  dmi.sys.vendor: Dell Inc.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777204/+subscriptions

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

Title:
  package linux-image-4.15.0-23-lowlatency (not installed) failed to
  install/upgrade: installed linux-image-4.15.0-23-lowlatency package
  pre-removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Known bug, worked around by removing old kernels.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-23-lowlatency (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-24.26-lowlatency 4.15.18
  Uname: Linux 4.15.0-24-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2193 F pulseaudio
mlthost2767 F pulseaudio
  Date: Fri Jun 15 19:32:44 2018
  ErrorMessage: installed 

[Kernel-packages] [Bug 1777257] Re: Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

[Christopher M. Penalver]

Merlin:

1) For you personally with your hardware, what was the most recent
kernel/release where this issue did not happen?

2) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full manufacturer and model?

3) How are you connecting the laptop to the monitor, via straight HDMI
cord, adapter/dongle, etc.?

** Tags added: bios-outdated-a10

** Tags added: regression-release

** Description changed:

- When booting 18.04 on my Dell 5737 I am greeted with an image like the
- attached. The colours are clearly incorrect and the display looks to be
- of low resolution. This is true whether booting from a fresh
- distribution copy on a memory stick or the subsequent patched install.
+ When booting 18.04 on my Dell 5737 built-in screen the colours are incorrect 
and the display looks to be of low resolution. This is true whether booting 
from a fresh distribution copy on a memory stick or the subsequent patched 
install. A screenshot:
+ https://launchpadlibrarian.net/374791190/2018-06-16%2016.46.54.jpg
+ 
  The image on an external monitor appears unaffected.
  
- This looks like a reappearance of
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
- https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
- to have the same issue on a similar machine:
- https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
- installing-18-04-on-dell-inspiron-3737/1047143#1047143
+ WORKAROUND: Use kernel parameter:
+ nomodeset
  
- Adding "nomodeset" does make the machine usable but obviously isn't
- ideal.
- 
- "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  merlin 1635 F pulseaudio
-  /dev/snd/controlC1:  merlin 1635 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  merlin 1635 F pulseaudio
+  /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-23-generic N/A
-  linux-backports-modules-4.15.0-23-generic  N/A
-  linux-firmware 1.173.1
+  linux-restricted-modules-4.15.0-23-generic N/A
+  linux-backports-modules-4.15.0-23-generic  N/A
+  linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 built-in screen the colours are incorrect 
and the display looks to be of low resolution. This is true whether booting 
from a fresh distribution copy on a memory stick or the subsequent patched 
install. A screenshot:
  https://launchpadlibrarian.net/374791190/2018-06-16%2016.46.54.jpg

  The image on an external monitor appears unaffected.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: 

[Kernel-packages] [Bug 1777634] Re: no more than 1 GATT descriptor allowed

[Daniel van Vugt]

Also, please report the bug to upstream here:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers=Bluetooth

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

Title:
  no more than 1 GATT descriptor allowed

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  By running the example-gatt-server and example-gatt-advertising,
  it was impossible to get more than one Descriptor per characteristic.
  if i comment one i can see the other in the test characteristic.
  but if i set both, it just act like no descriptor available.

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

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

[Kernel-packages] [Bug 1777634] Re: no more than 1 GATT descriptor allowed

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1777634

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  no more than 1 GATT descriptor allowed

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  By running the example-gatt-server and example-gatt-advertising,
  it was impossible to get more than one Descriptor per characteristic.
  if i comment one i can see the other in the test characteristic.
  but if i set both, it just act like no descriptor available.

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

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

[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G

[Peter Silva]

tried nomodeset.  now there is no mode set while booting, and goes into a boot 
loop.
then updated motherboard bios (april one.) repeat, and now it crashes to 
(initramfs)

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

Title:
  Cannot boot/install AMD Ryzen 2400G

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years 
or so. Now it only runs windows (same hardware fresh installs windows with no 
issue). brand new ryzen 2nd gen with graphics.
   
  I know about graphics drivers issues, wasn't expecting that to be dealt with.
  Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 
pitcairn) video card to get some functionality.

  Without the video card, it boots, but the display is unusable. I can
  ssh in and see that it works fine as a server, but cannot use terminal
  or graphical display.

  With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu",
  and it goes into an infinite loop. photo attached.  I tried 16.04.4 and
  I think it just went into a blank screen.

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

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

[Kernel-packages] [Bug 1775772] Re: Atheros Wireless ath9k random segmentation fault ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common]

[Christopher M. Penalver]

Kafabih Rahmat, to confirm, when you were using the previous release
Ubuntu 16.04.1, did this issue not happen?

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

Title:
  Atheros Wireless ath9k random segmentation fault
  ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, I got random segmentation fault on my Wireless card Atheros QCA9565 / 
AR9565 here I also attached dmesg and another logs.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CRDA:
   global
   country 98: DFS-UNSET
(2402 - 2472 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-14 (64 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20369
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (50 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20369
  dmi.product.version: Lenovo G40-70
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1775772] Re: Atheros Wireless ath9k random segmentation fault ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common]

[Christopher M. Penalver]

** Tags removed: kernel-bug-exists-upstream-4.17.2 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.18-rc1

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

Title:
  Atheros Wireless ath9k random segmentation fault
  ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, I got random segmentation fault on my Wireless card Atheros QCA9565 / 
AR9565 here I also attached dmesg and another logs.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CRDA:
   global
   country 98: DFS-UNSET
(2402 - 2472 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-14 (64 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20369
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (50 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20369
  dmi.product.version: Lenovo G40-70
  dmi.sys.vendor: LENOVO

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

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

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

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

Title:
  4.15.0-23-generic fails to PXE boot on PPC64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The MAAS CI has a PPC64 machine which is failing to boot into the
  ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic
  from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded.

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

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

[Kernel-packages] [Bug 1770029] Re: broadcom-sta-dkms 6.30.223.271-3~16.04.2: broadcom-sta kernel module failed to build [error: implicit declaration of function ‘init_timer’]

[rasaborio]

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

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

Title:
  broadcom-sta-dkms 6.30.223.271-3~16.04.2: broadcom-sta kernel module
  failed to build [error: implicit declaration of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  New
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  It was updating the system.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: broadcom-sta-dkms 6.30.223.271-3~16.04.2
  ProcVersionSignature: Ubuntu 4.15.0-13.14~16.04.1-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-20-generic
  Date: Tue May  8 23:00:41 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature: 
dkms:broadcom-sta-dkms:6.30.223.271-3~16.04.2:/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:2352:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-05-31 (342 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  PackageVersion: 6.30.223.271-3~16.04.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: broadcom-sta
  Title: broadcom-sta-dkms 6.30.223.271-3~16.04.2: broadcom-sta kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1777744] [NEW] 4.15.0-23-generic fails to PXE boot on PPC64

[Lee Trager]

Public bug reported:

The MAAS CI has a PPC64 machine which is failing to boot into the
ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic
from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded.

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


** Tags: bionic

** Attachment added: "consolelog"
   https://bugs.launchpad.net/bugs/144/+attachment/5154433/+files/consolelog

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

Title:
  4.15.0-23-generic fails to PXE boot on PPC64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The MAAS CI has a PPC64 machine which is failing to boot into the
  ephemeral environment. Petite boot loads and kexecs 4.15.0-23-generic
  from 4.4.27-openpower1 but 4.15 panics before the initrd is loaded.

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

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

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

[Taylor Raack]

Confirmed with a Lenovo V570 that using the generic HWE 16.04 edge
kernel restores hibernation ability. I needed to install both linux-
image-generic-hwe-16.04-edge" and "linux-headers-generic-
hwe-16.04-edge".

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

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

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

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

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

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

[bugproxy]

--- Comment From maur...@br.ibm.com 2018-06-19 19:30 EDT---
And patch is applied to bionic master-next. see
http://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/drivers/net/ethernet/intel/ixgbe?h=master-next=123dad8e7f35b815fdf6d0647b056c096f14d052

Thank you,

Mauro

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

Title:
  [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-
  jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)

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

Bug description:
  == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 ==
  Problem:
  
  Injecting error multiple times causes kernel crash.

  echo 0x0:1:4:0x60800:0xfff8 >
  /sys/kernel/debug/powerpc/PCI/err_injct

  EEH: PHB#0 failure detected, location: N/A
  EEH: PHB#0-PE#0 has failed 6 times in the
  last hour and has been permanently disabled.
  EEH: Unable to recover from failure from PHB#0-PE#0.
  Please try reseating or replacing it
  ixgbe :01:00.1: Adapter removed
  kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352!
  Oops: Exception in kernel mode, sig: 5 [#1]
  LE SMP NR_CPUS=2048 NUMA PowerNV
  Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds 
mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf 
ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq 
vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ib_iser 
rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx 
ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect 
sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum 
drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio
  CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu
  NIP:  c077f080 LR: c077f070 CTR: c00aac30
  REGS: c00ff1deb5a0 TRAP: 0700   Not tainted  (4.15.0-10-generic)
  MSR:  90029033   CR: 24002822  XER: 2004
  CFAR: c018bddc SOFTE: 1
  GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00
  GPR04: 02c5   
  GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488
  GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0
  GPR16:    
  GPR20:    c0f48d10
  GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000
  GPR28: c000200e4fcf4288 c00810624480  c00fbb633ea0
  NIP [c077f080] free_msi_irqs+0xa0/0x260
  LR [c077f070] free_msi_irqs+0x90/0x260
  Call Trace:
  [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable)
  [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170
  [c00ff1deb8c0] [c0081060b5c8] 
ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe]
  [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe]
  [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110
  [c00ff1deb9d0] [c085d194] 
device_release_driver_internal+0x224/0x310
  [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0
  [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40
  [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130
  [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130
  [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580
  [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338
  [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200
  [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0
  [c00ff1debe30] [c000b528] ret_from_kernel_thread+0x5c/0xb4
  Instruction dump:
  419effe0 3bc0 480c 6042 807f0010 7c7e1a14 78630020 4ba0cd3d
  6000 e9430158 312a 7d295110 <0b09> 813f0014 395e0001 7d5e07b4
  ---[ end trace 23c446a470e60864 ]---
  ixgbe :01:00.0: Adapter removed

  Sending IPI to other CPUs
  OPAL: Switch to big-endian OS
  OPAL: Switch to little-endian OS
  PHB#[0:0]: eeh_freeze_clear on fenced PHB

   
  ---uname output---
  Linux ltciofvtr-bostonlc1 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 
18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston-LC 

  :00:00.0 PCI bridge [0604]: IBM Device [1014:04c1]
  :01:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 

[Kernel-packages] [Bug 1775443] Re: Ubuntu 18.04 Bluetooth Crash

[Curtis]

After testing for the last week, the new kernel has not completely
solved the problem, though bluetooth does crash less frequently (once
every day or two instead of multiple times per day) when using the new
kernel.

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

Title:
  Ubuntu 18.04 Bluetooth Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am having trouble with the bluetooth connection between the laptop
  and my Logitech MX Master wireless mouse. The computer will lose
  connection with the mouse multiple times per day. When this happens,
  the bluetooth icon in the upper right-hand corner of the screen
  disappears. Checking the Bluetooth system preference panel, Bluetooth
  is turned off. I can toggle the switch to "on" but bluetooth remains
  off. Neither restarting the computer nor power cycling the computer
  bring bluetooth back. $ sudo service bluetooth restart also doesn't
  work. The only way I have found to renable bluetooth is:

  1. reboot
  2. disable bluetooth in BIOS
  3. reboot
  4. enable bluetooth in BIOS
  5. reboot

  Also, I was running Ubuntu 16.04 until this past Friday. I experienced
  this problem under 16.04 but it happened much less frequently (once
  every couple weeks or so). I upgraded to 18.04 ahead of 18.04.1 in
  hopes that a newer kernel/driver would work better with my brand new
  hardware. Now, under 18.04, bluetooth is crashing multiple times per
  day.

  Here's the output of `grep blue /var/log/syslog`:
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:dev_class_changed_callback() Class: 0x00
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:new_settings_callback() Settings: 0x0ada
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:settings_changed() Changed settings: 0x0001
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:cancel_passive_scanning()
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:adapter_remove_connection()
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:adapter_remove_connection()
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() 
adapter /org/bluez/hci0 has been disabled
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/device.c:att_disconnected_cb()
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/device.c:att_disconnected_cb() Software caused connection abort (103)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: 
connected -> disconnecting (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: 
disconnecting -> disconnected (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: 
connected -> disconnecting (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: 
disconnecting -> disconnected (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: 
connected -> disconnecting (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: 
disconnecting -> disconnected (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: 
connected -> disconnecting (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 
0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: 
disconnecting -> disconnected (0)
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning 
up.
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:index_removed() index 0
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 
src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() 
Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61
  Jun  6 09:12:41 Precision-5520 bluetoothd[3189]: 

[Kernel-packages] [Bug 1777736] [NEW] hisi_sas_v3_hw: internal task abort: timeout and not done.

[dann frazier]

Public bug reported:

[Impact]
On deployments with lots of disks, timeouts can occur that escalate into nexus 
resets. This can cause disk devices to disappear from the system, possibly 
requiring a reboot to recover:

[18324.951189] cq: iptt:892, task:8026fbde5000, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:16,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
[18324.951190] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
[18324.951191] cmd table: 0x0,0x0,0x0,0x0,0x0
[18324.951192] itct: 
0x12fa0345,0x5000cca25d31dac1,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
[18324.951334] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8026fbde5000) ignored

[18325.039774] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
[18325.044467] cmd table: 0x0,0x0,0x0,0x0,0x0
[18325.048553] itct: 
0x12fa0345,0x5000c50094c65c55,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
[18325.057058] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8027dc8e7500) ignored

[18326.951312] cq: iptt:1705, task:8027820d0200, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:18,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
[18326.968247] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
[18326.972938] cmd table: 0x0,0x0,0x0,0x0,0x0
[18326.977023] itct: 
0x12fa0345,0x5000cca0803e9c1d,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
[18326.985496] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8027820d0200) ignored

[18329.384695] hisi_sas_v3_hw :74:02.0: internal task abort: timeout and 
not done.
[18329.392344] hisi_sas_v3_hw :74:02.0: start dump all regs,reason:abort 
timeout!
[18329.399904] ***DUMP IS DISABLED***
[18329.405467] dump reg fail.
[18329.408162] hisi_sas_v3_hw :74:02.0: I_T nexus reset: internal abort (-5)
[18329.936017] cq: iptt:649, task:8027981f8500, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:19,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
[18329.936154] cq: iptt:1091, task:8026ff666d00, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:49,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
[18329.936155] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
[18329.936156] cmd table: 0x0,0x0,0x0,0x0,0x0
[18329.936158] itct: 
0x12fa0345,0x5000cca2552b2855,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
[18329.936301] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8026ff666d00) ignored

[Test Case]
This was seen on a system with 100s of disks, something I don't have access to, 
so verification testing will be regression-only.

[Fix]
A fix queued in the scsi maintainer's tree adjusts some magic registers in the 
controller, and that somehow fixes the problem (I don't have programming docs 
for this controller, so I can only hand-wave here).

[Regression Risk]
The fix is localized to the hisi_sas_v3_hw driver, which is only used in Ubuntu 
for the D06 platform.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Summary changed:

- hisi_sas: 
+ hisi_sas_v3_hw: internal task abort: timeout and not done.

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

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

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

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

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

Title:
  hisi_sas_v3_hw: internal task abort: timeout and not done.

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

Bug description:
  [Impact]
  On deployments with lots of disks, timeouts can occur that escalate into 
nexus resets. This can cause disk devices to disappear from the system, 
possibly requiring a reboot to recover:

  [18324.951189] cq: iptt:892, task:8026fbde5000, cmp_st:3, 
err_rcrd_xfrd:1,rspns_xfrd:0,error_phase:6,devid:16,io_cfg_err_code:0,err_code:0,
 ft = 0x0, ata_st=0x0, tgt_io_st=0x0,disk_err=0x0
  [18324.951190] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
  [18324.951191] cmd table: 0x0,0x0,0x0,0x0,0x0
  [18324.951192] itct: 
0x12fa0345,0x5000cca25d31dac1,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
  [18324.951334] hisi_sas_v3_hw :74:02.0: slot complete: 
task(8026fbde5000) ignored

  [18325.039774] sb dw0:0x8001,dw1:0x0,dw2:0x0,dw3:0x0
  [18325.044467] cmd table: 0x0,0x0,0x0,0x0,0x0
  [18325.048553] itct: 
0x12fa0345,0x5000c50094c65c55,0x11388,0x0,0x0,0x0,0x0,0x0,0x0,0x0
  [18325.057058] 

[Kernel-packages] [Bug 1777734] [NEW] hisi_sas: Add missing PHY spinlock init

[dann frazier]

Public bug reported:

[Impact]
This is a code correctness issue found during code review. From my reading of 
the code, the spin_lock will always happen to have just been devm_kcalloc'd, 
which uses GFP_ZERO, before spin_lock_init() needs to be called. That may make 
the current code safe, but relying on that coincidence seems dangerous. There's 
also various debugging facilities in the kernel that appear to rely on proper 
spinlock initialization, and those may currently be broken.

[Test Case]
Boot test to look for regressions.

[Fix]
Backport a fix from the scsi maintainer's 4.19 queue which adds a 
spin_lock_init() call.

[Regression Risk]
The fix is limited to the hisi_sas driver and is obviously correct.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

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

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

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

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

Title:
  hisi_sas: Add missing PHY spinlock init

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

Bug description:
  [Impact]
  This is a code correctness issue found during code review. From my reading of 
the code, the spin_lock will always happen to have just been devm_kcalloc'd, 
which uses GFP_ZERO, before spin_lock_init() needs to be called. That may make 
the current code safe, but relying on that coincidence seems dangerous. There's 
also various debugging facilities in the kernel that appear to rely on proper 
spinlock initialization, and those may currently be broken.

  [Test Case]
  Boot test to look for regressions.

  [Fix]
  Backport a fix from the scsi maintainer's 4.19 queue which adds a 
spin_lock_init() call.

  [Regression Risk]
  The fix is limited to the hisi_sas driver and is obviously correct.

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

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

[Kernel-packages] [Bug 1777242] Re: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

[Aurélien COUDERC]

Hmm, I had missed that :

$ sudo update-initramfs -u -k 4.15.0-23-generic 
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
modinfo: ERROR: could not get modinfo from 'qxl': Exec format error
depmod: ERROR: failed to load symbols from 
/var/tmp/mkinitramfs_a65BM0/lib/modules/4.15.0-23-generic/kernel/drivers/gpu/drm/qxl/qxl.ko:
 Exec format error

Side note : all upstream kernel packages I tested *do* boot correctly:
- 4.15.16, 4.15.17, 4.15.18
- 4.16.16
- 4.17.2

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

Title:
  4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

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

Bug description:
  Trying to boot bionic with 4.15.0-23-generic fails with a kernel panic in 
qemu on an Debian amd64 host.
  The version of qemu is the current in Debian Testing: 2.12+dfsg-3.

  Booting with 4.15.0-22-generic works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zouzou 1274 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-12 (338 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170710)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux-signed (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=26da642a-bbc4-440b-bed3-a911bbbfe582 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.11.1-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.8
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.1-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.8
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1777679] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard

[Alistair Sutter]

Update: Bug seems to be related to i2c-hid

Cannot boot properly with i2c-hid. Had to blacklist i2c-hid a while ago.
Un-blacklisting i2c-hid causes boot to fail with black-screen with ctrl+alt+f* 
combos unresponsive.

I don't know how to debug i2c-hid since the black-screen stops me from
accessing anything even terminal login.

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

[User Unknown]

@perryhelionsemail - I am really hesitant to removing the max_cstate
boot flag: I had to set this in order to avoid random and total system
freezes. And that bug seems to be anything but fixed:
https://bugzilla.kernel.org/show_bug.cgi?id=109051

So, with due respect to curiosity – not gonna try that. ;)

However, it seems I found a solution for now for my flickering graphics
issues.

I tried Gnome Shell (Ubuntu's default DE). There I did NOT encounter any
flickering.

But Gnome Shell isn't a Desktop Environment I would want to settle on –
I'll save you my random rant about it. :) And that was not my solution.

In trying to find a fix for my previously mentioned Cinnamon login-crash
bug, I had upgraded Cinnamon to the latest stable version 3.8.3 via a
PPA (the current version in Ubuntu's repo is 3.6.7). Today, I purged the
PPA and downgraded Cinnamon to the older Ubuntu's repo version. As a
result, the flickering issues with the patched kernel seem to be gone,
so I'm mostly good for now, as far as I can see. :)

To summarize:

- The patched 4.15.0-24 kernel enables me to suspend-to-ram.
- The patched 4.15.0-24 kernel brings a new issue for me: A minute-long wait 
before I get to the Ubuntu greeter and am able to login to a DE. This does not 
happen in 4.15.0-23.
- The patched 4.15.0-24 in combination with latest Cinnamon 3.8.3 (via PPA) 
causes graphics flickering big time. This does not occur in 4.15.0-23, either.

So, while indeed restoring suspend, the patch still seems to be missing
something.

@kaihengfeng - Is there any way I might help debugging or provide
additional info?

** Bug watch added: Linux Kernel Bug Tracker #109051
   https://bugzilla.kernel.org/show_bug.cgi?id=109051

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Kubuntu 18.04 on 3 different machines (my friend's
  and my own) with no suspend problems but my HP Pavilion 11 x360 does
  not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  
  Correct behaviour is - 

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  
  What happens - 

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  
  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  
  Checking the logs suggests that the machine believes it is in suspend mode 
sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na 
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

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

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

[Kernel-packages] [Bug 1777727] [NEW] hisi_sas: improve read performance by pre-allocating slot DMA buffers

[dann frazier]

Public bug reported:

[Impact]
Read performance is ~9% slower than it could be, as measured by the iozone3 
benchmark.

[Test Case]
iozone -a

I suggest collecting 5 runs of this, with and without the patch, and generating 
a report using:
https://github.com/Rovanion/iozone-results-comparator/wiki/Overview

[Fix]
Apply a patch queued in the scsi tree that pre-allocates DMA slot buffers.

[Regression Risk]
As called out in the commit log, the trade-off here is static memory usage, 
which could grow by ~17MB. However, as also noted, this method actually uses 
*less* memory than the baseline when all slots are allocated (32MB). (Ubuntu 
uses a 4K kernel).

The required fixes are localized to the hisi_sas driver. This driver is
only used by two platforms supported by Ubuntu: HiSilicon D05 and
HiSilicon D06. We will directly verify these fixes on those platforms.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

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

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

Title:
  hisi_sas: improve read performance by pre-allocating slot DMA buffers

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

Bug description:
  [Impact]
  Read performance is ~9% slower than it could be, as measured by the iozone3 
benchmark.

  [Test Case]
  iozone -a

  I suggest collecting 5 runs of this, with and without the patch, and 
generating a report using:
  https://github.com/Rovanion/iozone-results-comparator/wiki/Overview

  [Fix]
  Apply a patch queued in the scsi tree that pre-allocates DMA slot buffers.

  [Regression Risk]
  As called out in the commit log, the trade-off here is static memory usage, 
which could grow by ~17MB. However, as also noted, this method actually uses 
*less* memory than the baseline when all slots are allocated (32MB). (Ubuntu 
uses a 4K kernel).

  The required fixes are localized to the hisi_sas driver. This driver
  is only used by two platforms supported by Ubuntu: HiSilicon D05 and
  HiSilicon D06. We will directly verify these fixes on those platforms.

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

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

[Kernel-packages] [Bug 1777364] Re: coping files to cifs mounted directory causes general protection fault

[Martin Barlow]

I grabbed the latest 4.18.0-041800rc1 and recreated it quickly

I attach the output from syslog. Let me know what else i can provide to
be of assistance.

** Attachment added: "gpf with latest kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777364/+attachment/5154405/+files/gpf.4.18.0-041800rc1-generic.txt

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

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

Title:
  coping files to cifs mounted directory causes general protection fault

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  Copy some large files from local filesystem to CIFS mounted
  filesystem. After some gigabytes, it syslog will show "general
  protection fault" and mounted file system will become unresponsive.

  How often does it occur:

  Every time, after a few minutes or so.

  Affected kernels:

  Bionic 4.15.0-23-generic and forward. I also tried 4.15.18-041518-generic and 
4.16.13-041613-generic from ubuntu archives an got similar GPF.
  4.13.0-43-generic from ubuntu 17.10 not affected.

  More information:

  I have kerberos authenticated, autofs mounted, cifs
  Mounted with:
  type cifs 
(rw,relatime,vers=default,sec=krb5,cache=strict,username=root,uid=1100,forceuid,gid=0,noforcegid,addr=192.168.50.2,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mbarlow2249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jun 17 23:14:02 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=25088f17-7123-46c8-bda4-362bcd9f986e
  InstallationDate: Installed on 2017-11-26 (203 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=69170b9c-88cc-4e5b-83a8-c6a01d7b738b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (51 days ago)
  WifiSyslog:

  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 06CC14
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1777679] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard

[Alistair Sutter]

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1777679] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard

[Alistair Sutter]

As stated in the bug description this was already tested on kernel 4.17,
unsuccessfully.

kernel-bug-exists-upstream

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Maurice]

Sorry, the correct package in the post above is called "linux-image-
generic-hwe-16.04-edge".

Edge is important so you get the newest version.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

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

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

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

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

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

[Maurice]

Now, there is a solution for all people on Ubuntu 16.04.

You can now install the package "linux-image-generic-hwe-16.04" and it's
recommended dependencies. The package contains Kernel 4.15 which will
make hibernate work again.

Just tested and confirmed on Lenovo Y580 with Ubuntu 16.04.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1777689] Re: USB-Storage Quirk for 0bc2:2322 and 0bc2:61b7

[Joseph Salisbury]

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel


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

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
   Status: Confirmed

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

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

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

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

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

Title:
  USB-Storage Quirk for 0bc2:2322 and 0bc2:61b7

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

Bug description:
  Hi all,

  i've two usb3 connected in my Nuc.

  First : https://www.seagate.com/consumer/play/game-drive-xbox/#features
  Second : 
https://maxtor.seagate.com/files/maxtor-content/homepage/content/pdf/DS1879_1_1512US_M3Portable.pdf

  
  I blacklistet with this option in /etc/modprobe.d/uas-ignore-usbexternal.conf 
:

  options usb-storage quirks=0bc2:2322,0bc2:61b7:u

  The only problem that only works on the second device :

  $ dmesg | grep Quirks
  [2.743539] usb-storage 2-3:1.0: Quirks match for vid 0bc2 pid 61b7: 80

  I tried with these kernels :

  - 4.15.023
  - 4.17.0
  - 4.17.1
  - 4.17.2
  - 4.18-rc1

  Some info :

  $ sudo lsusb
  Bus 002 Device 003: ID 0bc2:2322 Seagate RSS LLC
  Bus 002 Device 002: ID 0bc2:61b7 Seagate RSS LLC
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
  Bus 001 Device 002: ID 20a0:0006 Clay Logic
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I have attached DMESG and various logs

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

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

[Kernel-packages] [Bug 1777679] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1


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

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

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1

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

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

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

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

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

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

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers

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

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

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

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

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

[Daniel Buchmann]

Jeremy, very good question :-), please see the results here:
http://shorturl.at/tGJKT

I did not post the results due to the large volume of text

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

Title:
  Bluetooth not working

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

Bug description:
  == SRU Justification ==
  A regression was discovered in Bionic.  The regression was introduced by
  mainline commit f44cb4b19ed4, which then made it's way into Bionic in
  4.15.0-14 as commit c91729972ac6 via stable updates.

  This regression is fixed by mainline commit 803cdb8ce584.  Commit
  803cdb8ce584 was also cc'd to stable.  However, it has not landed in
  upstream stable 4.15 or Bionic.

  
  == Fix ==
  803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 
models")

  
  == Regression Potential ==
  Low.  This fix has also been cc'd to upstream stable, so it has had
  additonal upstream review.

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



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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   

[Kernel-packages] [Bug 1774471] Re: Various fixes for CXL kernel module

[Frank Heimes]

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

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

Title:
  Various fixes for CXL kernel module

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

Bug description:

  == SRU Justification ==
  IBM is requesting the five patches in this pull request to be applied to 
Bionic.
  IBM states they patches fix various issues found after the 18.04 kernel 
freeze.

  == Regression Potential ==
  Low.  Limited to cxl driver.

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


  ---Problem Description---
  Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. 
They fix various issues found after the 18.04 kernel freeze:

  401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode
  497a0790e2c6 cxl: Report the tunneled operations status
  ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from 
cxllib
  02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9
  cxl: Configure PSL to not use APC virtual machines : 
http://patchwork.ozlabs.org/patch/899062/
  cxl: Disable prefault_mode in Radix mode : 
http://patchwork.ozlabs.org/patch/916159/

  ---uname output---
  4.15.0-12-generic

  ---Additional Hardware Info---
  a compatible capi FPGA adapter

  Machine Type = Boston-LC

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

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

[Kernel-packages] [Bug 1777716] Re: [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler

[Manoj Iyer]

Tested Bionic kernel on Cavium ThunderX2 with the patch.

ubuntu@starbuck:~$ uname -a 
Linux starbuck 4.15.0-25-generic #26~lp116+build.1 SMP Tue Jun 19 19:25:21 
UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$ dmesg | grep ipmi_ssif 
[   45.648719] ipmi_ssif: probe of dmi-ipmi-ssif.0 failed with error -17
[   45.648772] ipmi_ssif: probe of dmi-ipmi-ssif.1 failed with error -17
[   45.684502] ipmi_ssif: Trying SPMI-specified SSIF interface at i2c address 
0xe, adapter xlp9xx-i2c, slave address 0x0
[   45.804171] ipmi_ssif 0-000e: Found new BMC (man_id: 0x00, prod_id: 
0x0202, dev_id: 0x20)
ubuntu@starbuck:~$ lsmod | grep ssif
ipmi_ssif  40960  0
ipmi_msghandler61440  2 ipmi_ssif,ipmi_devintf
ubuntu@starbuck:~$

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

Title:
  [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  When you boot bionic with Boot with i2c and ipmi_ssif enabled on Cavium 
ThunderX2 systems with a faulty BMC that does not return any data, and the code 
is trying to print the value if data[2], we get a kernel panic.

  [  484.728410] Unable to handle kernel NULL pointer dereference at virtual 
address 0002
  [  484.736496] pgd = 094a2000
  [  484.739885] [0002] *pgd=0047fcffe003, *pud=0047fcffd003, 
*pmd=
  [  484.748158] Internal error: Oops: 9605 [#1] SMP
  [...]
  [  485.101451] Call trace:
  [...]
  [  485.188473] [] msg_done_handler+0x668/0x700 [ipmi_ssif]
  [  485.195249] [] ipmi_ssif_thread+0x110/0x128 [ipmi_ssif]
  [  485.202038] [] kthread+0x108/0x138
  [  485.206994] [] ret_from_fork+0x10/0x30
  [  485.212294] Code: aa1903e1 aa1803e0 b900227f 95fef6a5 (39400aa3)

  [Test]
  - System with faulty BMC
  - Boot with i2c and ipmi_ssif enabled.

  [Fix]
  Fixed upstream with:

  commit f002612b9d86613bc6fde0a444e0095225f6053e
  Author: Kamlakant Patel 
  Date: Tue Mar 13 16:32:27 2018 +0530

  ipmi_ssif: Fix kernel panic at msg_done_handler

  [Regression Potential]
  ipmi_ssif is only loaded on ARM64 systems, this issue is observed only on 
Cavium ThunderX2 systems with a faulty BMC. The fix does not impact other 
architectures or vendor systems. Regression potential is low.

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

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

[Kernel-packages] [Bug 1777238] Re: video lag

[Zoltán Süle]

I decided I add the tag: 'kernel-fixed-upstream', because I couldn't
reproduce it when I tested it 2nd and 3rd time for minutes.

** Tags added: kernel-fixed-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/1777238

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem exists for months and I didn't find a good answer on it.
  It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind
  the video the sounds continues, but the video stops), youtube,
  Hangouts and every software where video is played.

  I experienced that there are 2 things that can break it:
   - if I move the mouse out and in on the affected window (it doesn't work in 
full screen)
   - if I open the system monitor, the problem also disappears

  other people also face with this problem:
  
https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters
  
https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome
  
https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194
  https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04

  Ubuntu 4.15.0-23.25-generic 4.15.18
  it was upgraded from 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 14:34:26 2018
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2016-08-04 (680 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  vandor 3436 F pulseaudio
   /dev/snd/controlC1:  vandor 3436 F pulseaudio
   /dev/snd/controlC0:  vandor 3436 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c
  InstallationDate: Installed on 2016-08-04 (681 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1777238] Re: video lag

[Zoltán Süle]

Yes, this issue started after I upgraded my ubuntu from 16.04 to 18.04. I 
didn't experience it with 16.04.
I also have a newly installed 18.04 on a very same notebook and that one is 
also affected.

For the record: the youtube videos' lag issue was fixed weeks ago. I
just mentioned it, because I had a feeling that that was a similar bug.

I installed the '4.17.0-041700-generic' kernel. It fixed the problem partially:
- Cheese still stuck sometimes (very very rare), but continues in less than a 
second without interaction
- I cannot reproduce the issue with VLC and hangouts any more
- Super Tux Cart still affected (it might be a different issue?)

What should I do? Cheese works much better with the mainline kernel, but
it still stops sometimes for a moment.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem exists for months and I didn't find a good answer on it.
  It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind
  the video the sounds continues, but the video stops), youtube,
  Hangouts and every software where video is played.

  I experienced that there are 2 things that can break it:
   - if I move the mouse out and in on the affected window (it doesn't work in 
full screen)
   - if I open the system monitor, the problem also disappears

  other people also face with this problem:
  
https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters
  
https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome
  
https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194
  https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04

  Ubuntu 4.15.0-23.25-generic 4.15.18
  it was upgraded from 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 14:34:26 2018
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2016-08-04 (680 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  vandor 3436 F pulseaudio
   /dev/snd/controlC1:  vandor 3436 F pulseaudio
   /dev/snd/controlC0:  vandor 3436 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c
  InstallationDate: Installed on 2016-08-04 (681 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1777716] Re: [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler

[Manoj Iyer]

** Summary changed:

- [SRU][Bionic] kernel panic in ipmi_ssif at msg_done_handler
+ [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler

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

Title:
  [SRU Bionic][Cosmic] kernel panic in ipmi_ssif at msg_done_handler

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  When you boot bionic with Boot with i2c and ipmi_ssif enabled on Cavium 
ThunderX2 systems with a faulty BMC that does not return any data, and the code 
is trying to print the value if data[2], we get a kernel panic.

  [  484.728410] Unable to handle kernel NULL pointer dereference at virtual 
address 0002
  [  484.736496] pgd = 094a2000
  [  484.739885] [0002] *pgd=0047fcffe003, *pud=0047fcffd003, 
*pmd=
  [  484.748158] Internal error: Oops: 9605 [#1] SMP
  [...]
  [  485.101451] Call trace:
  [...]
  [  485.188473] [] msg_done_handler+0x668/0x700 [ipmi_ssif]
  [  485.195249] [] ipmi_ssif_thread+0x110/0x128 [ipmi_ssif]
  [  485.202038] [] kthread+0x108/0x138
  [  485.206994] [] ret_from_fork+0x10/0x30
  [  485.212294] Code: aa1903e1 aa1803e0 b900227f 95fef6a5 (39400aa3)

  [Test]
  - System with faulty BMC
  - Boot with i2c and ipmi_ssif enabled.

  [Fix]
  Fixed upstream with:

  commit f002612b9d86613bc6fde0a444e0095225f6053e
  Author: Kamlakant Patel 
  Date: Tue Mar 13 16:32:27 2018 +0530

  ipmi_ssif: Fix kernel panic at msg_done_handler

  [Regression Potential]
  ipmi_ssif is only loaded on ARM64 systems, this issue is observed only on 
Cavium ThunderX2 systems with a faulty BMC. The fix does not impact other 
architectures or vendor systems. Regression potential is low.

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

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

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

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

Title:
  [SRU][Bionic] kernel panic in ipmi_ssif at msg_done_handler

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  When you boot bionic with Boot with i2c and ipmi_ssif enabled on Cavium 
ThunderX2 systems with a faulty BMC that does not return any data, and the code 
is trying to print the value if data[2], we get a kernel panic.

  [  484.728410] Unable to handle kernel NULL pointer dereference at virtual 
address 0002
  [  484.736496] pgd = 094a2000
  [  484.739885] [0002] *pgd=0047fcffe003, *pud=0047fcffd003, 
*pmd=
  [  484.748158] Internal error: Oops: 9605 [#1] SMP
  [...]
  [  485.101451] Call trace:
  [...]
  [  485.188473] [] msg_done_handler+0x668/0x700 [ipmi_ssif]
  [  485.195249] [] ipmi_ssif_thread+0x110/0x128 [ipmi_ssif]
  [  485.202038] [] kthread+0x108/0x138
  [  485.206994] [] ret_from_fork+0x10/0x30
  [  485.212294] Code: aa1903e1 aa1803e0 b900227f 95fef6a5 (39400aa3)

  [Test]
  - System with faulty BMC
  - Boot with i2c and ipmi_ssif enabled.

  [Fix]
  Fixed upstream with:

  commit f002612b9d86613bc6fde0a444e0095225f6053e
  Author: Kamlakant Patel 
  Date: Tue Mar 13 16:32:27 2018 +0530

  ipmi_ssif: Fix kernel panic at msg_done_handler

  [Regression Potential]
  ipmi_ssif is only loaded on ARM64 systems, this issue is observed only on 
Cavium ThunderX2 systems with a faulty BMC. The fix does not impact other 
architectures or vendor systems. Regression potential is low.

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

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

[Kernel-packages] [Bug 1777716] [NEW] [SRU][Bionic] kernel panic in ipmi_ssif at msg_done_handler

[Manoj Iyer]

Public bug reported:

[Impact]
When you boot bionic with Boot with i2c and ipmi_ssif enabled on Cavium 
ThunderX2 systems with a faulty BMC that does not return any data, and the code 
is trying to print the value if data[2], we get a kernel panic.

[  484.728410] Unable to handle kernel NULL pointer dereference at virtual 
address 0002
[  484.736496] pgd = 094a2000
[  484.739885] [0002] *pgd=0047fcffe003, *pud=0047fcffd003, 
*pmd=
[  484.748158] Internal error: Oops: 9605 [#1] SMP
[...]
[  485.101451] Call trace:
[...]
[  485.188473] [] msg_done_handler+0x668/0x700 [ipmi_ssif]
[  485.195249] [] ipmi_ssif_thread+0x110/0x128 [ipmi_ssif]
[  485.202038] [] kthread+0x108/0x138
[  485.206994] [] ret_from_fork+0x10/0x30
[  485.212294] Code: aa1903e1 aa1803e0 b900227f 95fef6a5 (39400aa3)

[Test]
- System with faulty BMC
- Boot with i2c and ipmi_ssif enabled.

[Fix]
Fixed upstream with:

commit f002612b9d86613bc6fde0a444e0095225f6053e
Author: Kamlakant Patel 
Date: Tue Mar 13 16:32:27 2018 +0530

ipmi_ssif: Fix kernel panic at msg_done_handler

[Regression Potential]
ipmi_ssif is only loaded on ARM64 systems, this issue is observed only on 
Cavium ThunderX2 systems with a faulty BMC. The fix does not impact other 
architectures or vendor systems. Regression potential is low.

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


** Tags: bionic cavium

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

Title:
  [SRU][Bionic] kernel panic in ipmi_ssif at msg_done_handler

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  When you boot bionic with Boot with i2c and ipmi_ssif enabled on Cavium 
ThunderX2 systems with a faulty BMC that does not return any data, and the code 
is trying to print the value if data[2], we get a kernel panic.

  [  484.728410] Unable to handle kernel NULL pointer dereference at virtual 
address 0002
  [  484.736496] pgd = 094a2000
  [  484.739885] [0002] *pgd=0047fcffe003, *pud=0047fcffd003, 
*pmd=
  [  484.748158] Internal error: Oops: 9605 [#1] SMP
  [...]
  [  485.101451] Call trace:
  [...]
  [  485.188473] [] msg_done_handler+0x668/0x700 [ipmi_ssif]
  [  485.195249] [] ipmi_ssif_thread+0x110/0x128 [ipmi_ssif]
  [  485.202038] [] kthread+0x108/0x138
  [  485.206994] [] ret_from_fork+0x10/0x30
  [  485.212294] Code: aa1903e1 aa1803e0 b900227f 95fef6a5 (39400aa3)

  [Test]
  - System with faulty BMC
  - Boot with i2c and ipmi_ssif enabled.

  [Fix]
  Fixed upstream with:

  commit f002612b9d86613bc6fde0a444e0095225f6053e
  Author: Kamlakant Patel 
  Date: Tue Mar 13 16:32:27 2018 +0530

  ipmi_ssif: Fix kernel panic at msg_done_handler

  [Regression Potential]
  ipmi_ssif is only loaded on ARM64 systems, this issue is observed only on 
Cavium ThunderX2 systems with a faulty BMC. The fix does not impact other 
architectures or vendor systems. Regression potential is low.

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

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

[Kernel-packages] [Bug 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Thadeu Lima de Souza Cascardo]

I have been working on the backport for this to bionic and xenial, but
in order to do so, we are taking care of some build failures on the
latest version that we are going to add to cosmic. I'll update when
there is more progress on that.

Regards.
Cascardo.

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

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

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels (hwe-edge on xenial, for 
example; or the standard bionic kernel).

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.

  [Regression Potential]
  Analysis of crashed kernels will require that the crash file be moved to a 
system where crash doesn't have the regression. The patch, however, should 
touch only the broken command, and has been tested.

  -

  
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)

  crash> ?

  *  files  mach   repeat timer
  alias  foreachmodrunq   

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

[Thadeu Lima de Souza Cascardo]

I have been working on the backport for this to xenial, but in order to
do so, we are taking care of some build failures on the latest version
that we are going to add to cosmic. I'll update when there is more
progress on that.

Regards.
Cascardo.

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

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

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  New
Status in crash source package in Artful:
  In Progress
Status in crash source package in Bionic:
  Fix Released

Bug description:
  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)
   
  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8001-22C 

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

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

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)   
  WARNING: cannot access vmalloc'd module memory

  
  crash: invalid structure member offset: thread_info_task
 FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson 
Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

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

[Khaled El Mously]

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

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

Title:
  Bluetooth not working

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

Bug description:
  == SRU Justification ==
  A regression was discovered in Bionic.  The regression was introduced by
  mainline commit f44cb4b19ed4, which then made it's way into Bionic in
  4.15.0-14 as commit c91729972ac6 via stable updates.

  This regression is fixed by mainline commit 803cdb8ce584.  Commit
  803cdb8ce584 was also cc'd to stable.  However, it has not landed in
  upstream stable 4.15 or Bionic.

  
  == Fix ==
  803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 
models")

  
  == Regression Potential ==
  Low.  This fix has also been cc'd to upstream stable, so it has had
  additonal upstream review.

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



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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1770095] Re: Need fix to aacraid driver to prevent panic

[Khaled El Mously]

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

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

Title:
  Need fix to aacraid driver to prevent panic

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

Bug description:
  
  == SRU Justification ==
  A commit introduced in mainline v4.14-rc1 to aacraid
  (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a
  panic may happen under certain recovery situations.

  This regression is fixed by linux-next commit  7d3af7d96af7.

  
  == Fix ==
  7d3af7d96af7 ("scsi: aacraid: Correct hba_send to include iu_type")

  == Regression Potential ==
  Low.  This patch fixes a current regression.  It was cc'd to upstream
  stable, so it has had additonal upstream review.

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


  
  == Comment: #0 - Douglas Miller  - 2018-05-08 15:45:13 ==
  +++ This bug was initially created as a clone of Bug #167565 +++

  A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906)
  introduced a bug whereby a panic may happen under certain recovery
  situations. The following commit fixes that:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=7d3af7d96af7b9f51e1ef67b6f4725f545737da2

  We need this commit backported to Ubuntu 18.04

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

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

[Kernel-packages] [Bug 1773964] Re: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

[Khaled El Mously]

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

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

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

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

Bug description:
  == SRU Justification ==
  IBM is requesting these two commits in powerpc to fix an error they are
  seeing:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on 
  CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

  The first commit reduces some existing high latency delays.  The second
  commit fixes the fact that the OPAL RTC driver does not sleep in case it gets 
OPAL_BUSY or
  OPAL_BUSY_EVENT from firmware.

  == Fixes ==
  34dd25de9fe3 ("powerpc/powernv: define a standard delay for OPAL_BUSY type 
retry loops")
  682e6b4da5cb ("rtc: opal: Fix OPAL RTC driver OPAL_BUSY loops")

  == Regression Potential ==
  Low.  The first commit is specific to powerpc.  The second commit is, commit 
628daa8d5abf 
  and it been cc'd to upstream stable to fix a regression, so it has had
  additional upstream review.

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


  == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 ==
   State: Open by: swanman on 22 May 2018 09:17:33 

  Both w34 and wsbmc016 are stopped on this failure, where we get hung
  up on the following FFDC gathering step in the OS:

  #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command 
ppc64_cpu --frequency ignore_err=1
  #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency

  , and the last console output shows:
  # tail -200 /var/log/obmc-console.log
  s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989
  [13668.719850]  (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881)
  [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13732.630727]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=242996
  [13732.630757]  (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822)
  [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13795.649597]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=243942
  [13795.649631]  (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916)
  [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13860.140516]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=244940
  [13860.140557]  (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646)
  [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13924.731438]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=245874
  [13924.731484]  (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909)
  [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13988.642321]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=246892
  [13988.642362]  (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048)
  [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14052.661211]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=247857
  [14052.661266]  (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185)
  [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14115.680051]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=248819
  [14115.680085]  (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190)
  [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14180.154945]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=249833
  [14180.154986]  (detected by 132, t=3203473 jiffies, g=30289, c=30288, 
q=822138)
  [14244.968067]I F: Ne talls onCPUs/tasks
  [14244669838]   75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=2[14244.669944]  (detected by 3, t=3219600 jiffies, 
g=30289, c=30288, q=825384)
  [14308.748680] Id detected stalls on CPUs/tasks:
  [14308.748719]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=251755
  [14308.748755]  (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445)
  [14333.081775] Watchdog CPU:132 Hard LOCKUP
  [14344.750295] Watchdog CPU:132 became unstuck
  [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14372.735587]  75-: (5904 ticks this GP) 

[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.

[Khaled El Mously]

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

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

Title:
  kernel: Fix memory leak on CCA and EP11 CPRB processing.

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Description:  kernel: Fix memory leak on CCA and EP11 CPRB processing.
  Symptom:  Kernel memory not freed when CCA or EP11 CPRB processing fails.
  Problem:  kfree() in code error path missing.
  Solution: Slight rework of the malloc and free places.
  Reproduction: Run application which sends CCA or EP11 crypto requests
    to the crypto card(s). Now switch the cards offline with
    the help of chzcrypt. Monitor top or free output.

  Upstream commit(s): kernel 4.18
  89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21

  == Fix ==
  89a0c0ec0d2e ("s390/zcrypt: Fix CCA and EP11 CPRB processing failure memory 
leak.")

  == Regression Potential ==
  Low.  Limited to s390.

  == Test Case ==
  Verified upfront by IBM during upstream integration.

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

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

[Kernel-packages] [Bug 1770423] Re: Please cherry-pick upstream patch for HDMI on Dell XPS 9360

[Joseph Salisbury]

I built a Xenial test kernel with commit 
9a86cda07af2c63649932f0a4fc757701ef54c42.  The test kernel can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1770423

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

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

Thanks in advance!

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

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

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

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

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

Title:
  Please cherry-pick upstream patch for HDMI on Dell XPS 9360

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

Bug description:
  Connecting the Dell USB-C HDMI/LAN/VGA/USB adapter to my XPS 9360
  doesn’t quite work: I could not get my monitor to display a picture at
  all, regardless of which resolution I tried.

  A quick search on the internet revealed this patch:
  https://lists.freedesktop.org/archives/intel-
  gfx/2017-March/124077.html. Applying it to the 4.4.0-122 kernel does
  indeed make the HDMI work

  Could you please cherry-pick this patch into the Ubuntu kernel?
  Thanks!

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

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

[Kernel-packages] [Bug 1774471] Re: Various fixes for CXL kernel module

[Khaled El Mously]

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

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

Title:
  Various fixes for CXL kernel module

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

Bug description:

  == SRU Justification ==
  IBM is requesting the five patches in this pull request to be applied to 
Bionic.
  IBM states they patches fix various issues found after the 18.04 kernel 
freeze.

  == Regression Potential ==
  Low.  Limited to cxl driver.

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


  ---Problem Description---
  Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. 
They fix various issues found after the 18.04 kernel freeze:

  401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode
  497a0790e2c6 cxl: Report the tunneled operations status
  ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from 
cxllib
  02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9
  cxl: Configure PSL to not use APC virtual machines : 
http://patchwork.ozlabs.org/patch/899062/
  cxl: Disable prefault_mode in Radix mode : 
http://patchwork.ozlabs.org/patch/916159/

  ---uname output---
  4.15.0-12-generic

  ---Additional Hardware Info---
  a compatible capi FPGA adapter

  Machine Type = Boston-LC

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

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

[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0

[Ryan Finnie]

The fix was bikeshedded a tiny bit on LKML, but is now accepted upstream
and AIUI will be in linux-next soon:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?id=0d98ba8d70b0070ac117452ea0b663e26bbf46bf

This change is tested as backwards compatible with Ubuntu 4.15, and
would be appreciated for SRU.

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

Title:
  Reboot/shutdown kernel panic on HP DL360/DL380 Gen9 w/ bionic 4.15.0

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

Bug description:
  Verified on multiple DL360 Gen9 servers with up to date firmware.
  Just before reboot or shutdown, there is the following panic:

  [  289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 1
  [  289.093085] {1}[Hardware Error]: event severity: fatal
  [  289.093087] {1}[Hardware Error]:  Error 0, type: fatal
  [  289.093088] {1}[Hardware Error]:   section_type: PCIe error
  [  289.093090] {1}[Hardware Error]:   port_type: 4, root port
  [  289.093091] {1}[Hardware Error]:   version: 1.16
  [  289.093093] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  289.093094] {1}[Hardware Error]:   device_id: :00:01.0
  [  289.093095] {1}[Hardware Error]:   slot: 0
  [  289.093096] {1}[Hardware Error]:   secondary_bus: 0x03
  [  289.093097] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x2f02
  [  289.093098] {1}[Hardware Error]:   class_code: 040600
  [  289.093378] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  289.093380] {1}[Hardware Error]:  Error 1, type: fatal
  [  289.093381] {1}[Hardware Error]:   section_type: PCIe error
  [  289.093382] {1}[Hardware Error]:   port_type: 4, root port
  [  289.093383] {1}[Hardware Error]:   version: 1.16
  [  289.093384] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  289.093386] {1}[Hardware Error]:   device_id: :00:01.0
  [  289.093386] {1}[Hardware Error]:   slot: 0
  [  289.093387] {1}[Hardware Error]:   secondary_bus: 0x03
  [  289.093388] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x2f02
  [  289.093674] {1}[Hardware Error]:   class_code: 040600
  [  289.093676] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  289.093678] Kernel panic - not syncing: Fatal hardware error!
  [  289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [  289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.

  It does eventually restart after this.  Then during the subsequent
  POST, the following warning appears:

  Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
  Drive(s) - Operation Failed
   - 1719-Slot 0 Drive Array - A controller failure event occurred prior
 to this power-up.  (Previous lock up code = 0x13) Action: Install the
 latest controller firmware. If the problem persists, replace the
 controller.

  The latter's symptoms are described in
  https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
  but the running storage controller firmware is much newer than the
  doc's resolution.

  Neither of these problems occur during shutdown/reboot on the xenial
  kernel.

  FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
  (01/22/2018)), the shutdown failure mode was a loop like so:

  [529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
  [529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.222884] Do you have a strange power saving mode enabled?
  [529153.222884] Dazed and confused, but trying to continue
  [529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554448] Do you have a strange power saving mode enabled?
  [529153.554449] Dazed and confused, but trying to continue
  [529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554451] Do you have a strange power saving mode enabled?
  [529153.554452] Dazed and confused, but trying to continue
  [529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554453] Do you have a strange power saving mode enabled?
  [529153.554454] Dazed and confused, but trying to continue
  [529153.554454] Uhhuh. NMI received for unknown reason 35 on CPU 0.
  [529153.554455] Do you have a strange power saving mode enabled?
  [529153.554456] Dazed and confused, but trying to continue
  [529153.554457] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554458] Do you have a strange power saving mode enabled?
  [529153.554458] Dazed and confused, but trying to continue
  [529153.554459] Uhhuh. NMI received for unknown reason 25 on CPU 0.
  [529153.554460] Do you have a strange power saving mode enabled?
  [529153.554460] Dazed and 

[Kernel-packages] [Bug 1775391] Re: kernel: Fix arch random implementation

[Khaled El Mously]

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

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

Title:
  kernel: Fix arch random implementation

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM reports that arch_get_random_seed_long() invocations may slow down the
  interrupt handling on heavy interrupt producing loads.

  The existing random device driver calls arch_get_random_seed_long() in
  interrupt context. The current implementation of this function uses the
  PRNO(TRNG) instruction to provide good entropy. This instruction is
  relatively slow and expensive and may slow down the capacity of interrupts 
which can be handled per cpu.

  This fix reworks the arch_get_random_seed implementation.  It introduces a
  buffer concept to decouple the delivery of random data via
  arch_get_random_seed*() from the generation of new random bytes and so
  does not limit the interrupt handling per cpu any more.

  == Fix ==
  966f53e750ae ("s390/archrandom: Rework arch random implementation.")

  == Regression Potential ==
  Low.  This fix is limited to s390.

  == Test Case ==
  Verified upfront by IBM during upstream integration



  Description:  kernel: Fix arch random implementation
  Symptom:  arch_get_random_seed_long() invocations may slow down the
    interrupt handling on heavy interrupt producing loads.
  Problem:  The existing random device driver calls
    arch_get_random_seed_long() in interrupt context. The
    current implementation of this function uses the
    PRNO(TRNG) instruction to provide good entropy. This
    instruction is relatively slow and expensive and may
    slow down the capacity of interrupts which can be handled
    per cpu.
  Solution: This fix reworks the arch_get_random_seed implementation.
    It introduces a buffer concept to decouple the delivery
    of random data via arch_get_random_seed*() from the
    generation of new random bytes and so does not limit
    the interrupt handling per cpu any more.
  Reproduction: Systems with heavy irq load show performance decrease.
  Component:kernel

  Upstream commit(s): kernel 4.18
  966f53e750aedc5f59f9ccae6bbfb8f671c7c842

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

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

[Kernel-packages] [Bug 1773400] Re: Redpine: wifi-ap stopped working after restart

[Khaled El Mously]

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

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

Title:
  Redpine: wifi-ap stopped working after restart

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification:
  --

  Impact:
  Wi-Fi access point isn’t visible to outside devices after reboot

  Test Case:
  Configure Wi-Fi AP using setup wizard:
     $ sudo wifi-ap.setup-wizard

  Check configured AP settings:
     $ sudo wifi-ap.config get

     debug: false
     dhcp.lease-time: 12h
     dhcp.range-start: 10.0.60.2
     dhcp.range-stop: 10.0.60.200
     disabled: false
     share.disabled: false
     share.network-interface: wlan0
     wifi.address: 10.0.60.1
     wifi.channel: 6
     wifi.country-code:
     wifi.hostapd-driver: nl80211
     wifi.interface: wlan0
     wifi.interface-mode: direct
     wifi.netmask: ff00
     wifi.operation-mode: g
     wifi.security: wpa2
     wifi.security-passphrase: some-password
     wifi.ssid: dell-gateway

  Check in third-party stations. SSID is invisible.

  Restart AP and check its status:
     $ sudo wifi-ap.status restart-ap

  Check status of AP. It is showing true.
     $ sudo wifi-ap.status
     ap.active: true

  At this point also, Wi-Fi access point is not visible.

  Fix:
  Power save is enabled in AP mode. it must be disabled.

  Regression potential:
  Ran "wifi-ap.status restart-ap" command in every 1 minute and observed 
whether it is visible to third party devices are not. And it is behaving as 
expected.

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

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

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

[Kernel-packages] [Bug 1776389] Re: [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)

[Khaled El Mously]

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

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

Title:
  [Ubuntu 1804][boston][ixgbe] EEH causes kernel BUG at /build/linux-
  jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352 (i2S)

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

Bug description:
  == Comment: #0 - ABDUL HALEEM <> - 2018-02-16 08:26:15 ==
  Problem:
  
  Injecting error multiple times causes kernel crash.

  echo 0x0:1:4:0x60800:0xfff8 >
  /sys/kernel/debug/powerpc/PCI/err_injct

  EEH: PHB#0 failure detected, location: N/A
  EEH: PHB#0-PE#0 has failed 6 times in the
  last hour and has been permanently disabled.
  EEH: Unable to recover from failure from PHB#0-PE#0.
  Please try reseating or replacing it
  ixgbe :01:00.1: Adapter removed
  kernel BUG at /build/linux-jWa1Fv/linux-4.15.0/drivers/pci/msi.c:352!
  Oops: Exception in kernel mode, sig: 5 [#1]
  LE SMP NR_CPUS=2048 NUMA PowerNV
  Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache joydev input_leds 
mac_hid idt_89hpesx ofpart ipmi_powernv cmdlinepart ipmi_devintf 
ipmi_msghandler at24 powernv_flash mtd opal_prd ibmpowernv uio_pdrv_genirq 
vmx_crypto uio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ib_iser 
rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas qla2xxx 
ast hid_generic ttm drm_kms_helper ixgbe syscopyarea usbhid igb sysfillrect 
sysimgblt nvme_fc fb_sys_fops hid nvme_fabrics crct10dif_vpmsum crc32c_vpmsum 
drm i40e scsi_transport_fc aacraid i2c_algo_bit mdio
  CPU: 28 PID: 972 Comm: eehd Not tainted 4.15.0-10-generic #11-Ubuntu
  NIP:  c077f080 LR: c077f070 CTR: c00aac30
  REGS: c00ff1deb5a0 TRAP: 0700   Not tainted  (4.15.0-10-generic)
  MSR:  90029033   CR: 24002822  XER: 2004
  CFAR: c018bddc SOFTE: 1
  GPR00: c077f070 c00ff1deb820 c16ea600 c00fbb5fac00
  GPR04: 02c5   
  GPR08: c00fbb5fac00 0001 c00fec617a00 c00fdfd86488
  GPR12: 0040 c7a33400 c0138be8 c00ff90ec1c0
  GPR16:    
  GPR20:    c0f48d10
  GPR24: c0f48ce8 c000200e4fcf4000 c00fc6900b18 c000200e4fcf4000
  GPR28: c000200e4fcf4288 c00810624480  c00fbb633ea0
  NIP [c077f080] free_msi_irqs+0xa0/0x260
  LR [c077f070] free_msi_irqs+0x90/0x260
  Call Trace:
  [c00ff1deb820] [c077f070] free_msi_irqs+0x90/0x260 (unreliable)
  [c00ff1deb880] [c077fa68] pci_disable_msix+0x128/0x170
  [c00ff1deb8c0] [c0081060b5c8] 
ixgbe_reset_interrupt_capability+0x90/0xd0 [ixgbe]
  [c00ff1deb8f0] [c008105d52f4] ixgbe_remove+0xec/0x240 [ixgbe]
  [c00ff1deb990] [c07670ec] pci_device_remove+0x6c/0x110
  [c00ff1deb9d0] [c085d194] 
device_release_driver_internal+0x224/0x310
  [c00ff1deba20] [c075b398] pci_stop_bus_device+0x98/0xe0
  [c00ff1deba60] [c075b588] pci_stop_and_remove_bus_device+0x28/0x40
  [c00ff1deba90] [c005e1d0] pci_hp_remove_devices+0x90/0x130
  [c00ff1debb20] [c005e184] pci_hp_remove_devices+0x44/0x130
  [c00ff1debbb0] [c003ec04] eeh_handle_normal_event+0x134/0x580
  [c00ff1debc60] [c003f160] eeh_handle_event+0x30/0x338
  [c00ff1debd10] [c003f830] eeh_event_handler+0x140/0x200
  [c00ff1debdc0] [c0138d88] kthread+0x1a8/0x1b0
  [c00ff1debe30] [c000b528] ret_from_kernel_thread+0x5c/0xb4
  Instruction dump:
  419effe0 3bc0 480c 6042 807f0010 7c7e1a14 78630020 4ba0cd3d
  6000 e9430158 312a 7d295110 <0b09> 813f0014 395e0001 7d5e07b4
  ---[ end trace 23c446a470e60864 ]---
  ixgbe :01:00.0: Adapter removed

  Sending IPI to other CPUs
  OPAL: Switch to big-endian OS
  OPAL: Switch to little-endian OS
  PHB#[0:0]: eeh_freeze_clear on fenced PHB

   
  ---uname output---
  Linux ltciofvtr-bostonlc1 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 
18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston-LC 

  :00:00.0 PCI bridge [0604]: IBM Device [1014:04c1]
  :01:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit 
SFI/SFP+ Network Connection [8086:10fb] (rev 01)
  :01:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit 
SFI/SFP+ Network Connection [8086:10fb] (rev 01)

  # ethtool  -i enp1s0f0

[Kernel-packages] [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device

[Kai-Heng Feng]

If trying mainline kernel is not an option, wait for Cosmic (18.10).

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

Title:
  Linux reports Samson Meteor USB mic as an output device

Status in linux package in Ubuntu:
  Expired

Bug description:
  Whenever I reboot my system, pulseaudio selects my Samson Meteor USB
  mic as the default output device. I have to manually select the analog
  output every time. Also, the Default effect sound does not make any
  noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2355 F pulseaudio
   /dev/snd/controlC1:  guru   2355 F pulseaudio
   /dev/snd/controlC0:  guru   2355 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr 10 08:54:30 2018
  InstallationDate: Installed on 2018-04-07 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2402 F pulseaudio
   /dev/snd/controlC1:  guru   2402 F pulseaudio
   /dev/snd/controlC0:  guru   2402 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-07 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  IwConfig:
   enp30s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2402 F pulseaudio
   /dev/snd/controlC1:  guru   2402 F pulseaudio
   /dev/snd/controlC0:  guru   2402 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-07 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  IwConfig:
   enp30s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware  

[Kernel-packages] [Bug 1767324] Re: Extreme regression in battery autonomy with kernel 4.15

[Kai-Heng Feng]

Please find the first -rc kernel in [1] that introduces the issue:

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline

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

Title:
  Extreme regression in battery autonomy with kernel 4.15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to kernel 4.15, my laptop (HP Elitebook 850 G3) lasts
  less than one hour on a fully charged battery. On Ubuntu 17.10 with
  kernel 4.13, the autonomy was typically in excess of 5 hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-lowlatency 4.15.0.20.23
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jzimm  3538 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:10:02 2018
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 
radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-lowlatency N/A
   linux-backports-modules-4.15.0-20-lowlatency  N/A
   linux-firmware1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1777257] Re: Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

[Merlin]

apport-collect was run on an installed and fully patched system as it
did not appear to run correctly from the distribution memory stick. The
video behavior is identical in both cases.

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1777696] [NEW] hisi_sas: Failures during host reset

[dann frazier]

Public bug reported:

[Impact]
When error handling progresses to host reset, several issues may prevent the 
system from recovering, therefore requiring a system power cycle.

[Test Case]
$ iozone -a &
$ while :; do sudo sg_reset --device /dev/sda; sleep 5; done

[Fix]
There is a race between device removal and host reset which can cause the 
driver to hang, preventing the user from accessing attached devices until a 
reboot. Fix this by adding locking around the critical path.

After a soft host reset, commands maybe sent to the device before the
hardware is ready to receive them. This can result in additional errors
when the user access the device. Fix this by blocking commands until the
hardware has been reinitialized.

Stale PHY events may still get processed by the driver after reset. This
can cause e.g. ports to be detached because an old pre-reset "phy down"
event gets processed, causing the user to lose access to attached
devices. Fix this by filtering out pre-reset PHY events.

Resource starvation can occur after a "clear nexus ha" reset. Fix this
by releasing those resources during the reset.

[Regression Risk]
The required fixes are localized to the hisi_sas driver. This driver is only 
used by two platforms supported by Ubuntu: HiSilicon D05 and HiSilicon D06. We 
will directly verify these fixes on those platforms.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

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

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

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

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

Title:
  hisi_sas: Failures during host reset

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

Bug description:
  [Impact]
  When error handling progresses to host reset, several issues may prevent the 
system from recovering, therefore requiring a system power cycle.

  [Test Case]
  $ iozone -a &
  $ while :; do sudo sg_reset --device /dev/sda; sleep 5; done

  [Fix]
  There is a race between device removal and host reset which can cause the 
driver to hang, preventing the user from accessing attached devices until a 
reboot. Fix this by adding locking around the critical path.

  After a soft host reset, commands maybe sent to the device before the
  hardware is ready to receive them. This can result in additional
  errors when the user access the device. Fix this by blocking commands
  until the hardware has been reinitialized.

  Stale PHY events may still get processed by the driver after reset.
  This can cause e.g. ports to be detached because an old pre-reset "phy
  down" event gets processed, causing the user to lose access to
  attached devices. Fix this by filtering out pre-reset PHY events.

  Resource starvation can occur after a "clear nexus ha" reset. Fix this
  by releasing those resources during the reset.

  [Regression Risk]
  The required fixes are localized to the hisi_sas driver. This driver is only 
used by two platforms supported by Ubuntu: HiSilicon D05 and HiSilicon D06. We 
will directly verify these fixes on those platforms.

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

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

[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)

[Olaf Seibert]

Yes, the problem started after an upgrade. From what I can see in the logs it 
seems that first the machine was upgraded from Ubuntu 17.10 to 18.04, 
apparently without problem.
Then a few days later, the working kernel Ubuntu 4.13.0-43.48-generic 4.13.16 
was replaced by 4.15.0-23.25-generic 4.15.18 which fails.

It will not be so easy to test another kernel, but I'll try. It will
definitely be some days before I can report a result, I suspect.

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

Title:
  X freezes with kernel 4.15.0-23-generic (AMDGPU)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is on my parents machine; I only have remote access and not
  continuously, so this may slow down providing additional information.

  Since the latest kernel upgrade (from
   Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 
(Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 
4.13.0-43.48-generic 4.13.16)  
  to  
  Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 
4.15.0-23.25-generic 4.15.18)
  the machine appears to freezes some time soon after booting. It is just X; 
the machine is still reachable via ssh.

  I filed this bug using apport-cli, running the older (working) kernel,
  not the newer (failing) one.

  In /var/log/kernel I can see the following:

  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked 
for more than 120 seconds.
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396]   Not tainted 
4.15.0-23-generic #25-Ubuntu
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0   757   
 724 0x0044
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace:
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424]  __schedule+0x297/0x8b0
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430]  ? __kfifo_in+0x37/0x50
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434]  schedule+0x2c/0x80
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559]  
amd_sched_entity_push_job+0xad/0xf0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565]  ? wait_woken+0x80/0x80
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653]  amdgpu_job_submit+0x9f/0xc0 
[amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723]  
amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793]  ? 
amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863]  
amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930]  
amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962]  ? 
drm_gem_handle_create_tail+0x120/0x190 [drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028]  ? 
amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096]  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115]  drm_ioctl_kernel+0x5f/0xb0 
[drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134]  ? drm_ioctl_kernel+0x5f/0xb0 
[drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154]  drm_ioctl+0x31b/0x3d0 [drm]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220]  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225]  ? update_load_avg+0x57f/0x6e0
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231]  ? futex_wake+0x8f/0x180
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290]  amdgpu_drm_ioctl+0x4f/0x90 
[amdgpu]
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296]  do_vfs_ioctl+0xa8/0x630
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300]  ? __schedule+0x29f/0x8b0
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304]  SyS_ioctl+0x79/0x90
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309]  do_syscall_64+0x73/0x130
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313]  
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 
EFLAGS: 3246 ORIG_RAX: 0010
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 
0002 RCX: 7fbd7ddcf5d7
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: 
c0286448 RDI: 000e
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 
00010144 R09: 000a
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 
3246 R12: c0286448
  Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 
55e820965f20 R15: 0

  
  which seems to point to some in-kernel AMD GPU 

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1774336] Re: FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false

[David Coronel]

I have confirmation from a user running NFS stress tests on Xenial with
this kernel and has not seen any issues. Changed tag to verification-
done-xenial.

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

Title:
  FS-Cache: Assertion failed: FS-Cache: 6 == 5 is false

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==

  [Impact]
  Oops during heavy NFS + FSCache use:

  [81738.886634] FS-Cache: 
  [81738.888281] FS-Cache: Assertion failed
  [81738.889461] FS-Cache: 6 == 5 is false
  [81738.890625] [ cut here ]
  [81738.891706] kernel BUG at 
/build/linux-hVVhWi/linux-4.4.0/fs/fscache/operation.c:494!

  6 == 5 represents an operation being DEAD when it was not expected to
  be.

  [Cause]
  There is a race in fscache and cachefiles. 

  One thread is in cachefiles_read_waiter:
   1) object->work_lock is taken.
   2) the operation is added to the to_do list.
   3) the work lock is dropped.
   4) fscache_enqueue_retrieval is called, which takes a reference.

  Another thread is in cachefiles_read_copier:
   1) object->work_lock is taken
   2) an item is popped off the to_do list.
   3) object->work_lock is dropped.
   4) some processing is done on the item, and fscache_put_retrieval() is 
called, dropping a reference.

  Now if the this process in cachefiles_read_copier takes place
  *between* steps 3 and 4 in cachefiles_read_waiter, a reference will be
  dropped before it is taken, which leads to the objects reference count
  hitting zero, which leads to lifecycle events for the object happening
  too soon, leading to the assertion failure later on.

  (This is simplified and clarified from the original upstream analysis
  for this patch at https://www.redhat.com/archives/linux-
  cachefs/2018-February/msg1.html and from a similar patch with a
  different approach to fixing the bug at
  https://www.redhat.com/archives/linux-cachefs/2017-June/msg2.html)

  [Fix]
  Move fscache_enqueue_retrieval under the lock in cachefiles_read_waiter. This 
means that the object cannot be popped off the to_do list until it is in a 
fully consistent state with the reference taken.

  [Testcase]
  A user has run ~100 hours of NFS stress tests and not seen this bug recur.

  [Regression Potential]
   - Limited to fscache/cachefiles. 
   - The change makes things more conservative (doing more under lock) so 
that's reassuring. 
   - There may be performance impacts but none have been observed so far.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1777257/+attachment/5154356/+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/1777257

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

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

[Merlin]

apport information

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.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: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1777257] Re: Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

[Merlin]

apport information

** Tags added: apport-collected bionic

** Description changed:

  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to be
  of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.
  
  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143
  
  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.
  
  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  merlin 1635 F pulseaudio
+  /dev/snd/controlC1:  merlin 1635 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-04-28 (52 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ MachineType: Dell Inc. Inspiron 5737
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-23-generic N/A
+  linux-backports-modules-4.15.0-23-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  bionic
+ Uname: Linux 4.15.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: 08/25/2016
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A09
+ dmi.board.name: 0V3MXK
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.chassis.version: A09
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
+ dmi.product.family: 00
+ dmi.product.name: Inspiron 5737
+ dmi.product.version: A09
+ dmi.sys.vendor: Dell Inc.

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting 18.04 on my Dell 5737 I am greeted with an image like the
  attached. The colours are clearly incorrect and the display looks to
  be of low resolution. This is true whether booting from a fresh
  distribution copy on a memory stick or the subsequent patched install.
  The image on an external monitor appears unaffected.

  This looks like a reappearance of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300349 and
  https://ubuntuforums.org/showthread.php?t=2204287 Someone else appears
  to have the same issue on a similar machine:
  https://askubuntu.com/questions/1036968/no-red-color-on-screen-after-
  installing-18-04-on-dell-inspiron-3737/1047143#1047143

  Adding "nomodeset" does make the machine usable but obviously isn't
  ideal.

  "lsb_release -rd" gives Ubuntu 18.04 LTS release 18.04.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  

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

[Alistair Sutter]

apport information

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Alistair Sutter]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1777679/+attachment/5154334/+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/1777679

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Alistair Sutter]

apport information

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Alistair Sutter]

apport information

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Alistair Sutter]

apport information

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Alistair Sutter]

apport information

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Alistair Sutter]

apport information

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1777679] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized at ITE 8910 keyboard

[Alistair Sutter]

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

** Summary changed:

- ELAN1200 touchpad not working at all with kernel 4.15+; Recognized at ITE 
8910 keyboard
+ ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 
8910 keyboard

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

Title:
  ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as
  ITE 8910 keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is an Asus-GL503VD

  Touchpad is an ELAN touchpad model 1200.

  This bug is relative to the Asus-GL503VD and any Asus laptop using the
  ELAN1200 touchpad.

  I tried Arch, Debian, Ubuntu 14/16/18, Pop_OS, Sabayon Linux, Fedora.
  Same problem, touchpad is totally unresponsive.

  From what I understand the touchpad is being recognized as a keyboard
  and I cannot get any driver to recognize it: elan-i2c or synaptics.

  The touchpad is also being recognized as a USB device.

  This behaviour was consistent on kernels 4.15.0-22, 4.15.0-23 and 4.17.1.
  Right now trying to make it work on kernel 4.15.0-23 because it seems more 
"main-stream".

  Note: I have a keyboard recognized as AT Translated Set 2 keyboard
  which makes me believe I do not need ITE8910 to be a keyboard.

  Note2: Been researching LKM development. Managed to make a signed 'hello 
world' lkm and make it output in dmesg. Willing to help debug/develop the 
driver for this touchpad.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ttr1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7791e5a6-d685-49b9-93d7-017c1abf4b89
  InstallationDate: Installed on 2018-06-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=98160487-6d8d-429c-830c-035e5faeb890 ro CONFIG_MODVERSIONS=true 
nvidia.modeset=1 nouveau.modeset=0 acpi=force i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

[noreasternhumidty]

Thanks for confirming.  My resonse was mainly due to the latest Linux
Mint beta, which uses the 4.15 kernel as its base (there is no option to
go lower).  So this is something that they will have to eventually
solve.  I'll take a look there.

BTW The out-of-distro kernels installed by Ukuu broke my Apt system, I
wasn't able to install or remove any software until I used Ukuu to
remove the out-of-distro kernels.  So that isn't an option anyhow.

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Kubuntu 18.04 on 3 different machines (my friend's
  and my own) with no suspend problems but my HP Pavilion 11 x360 does
  not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  
  Correct behaviour is - 

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  
  What happens - 

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  
  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  
  Checking the logs suggests that the machine believes it is in suspend mode 
sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na 
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

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

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

[Kernel-packages] [Bug 1777689] Re: USB-Storage Quirk for 0bc2:2322 and 0bc2:61b7

[Stefano]

** Description changed:

  Hi all,
  
- i've thow usb3 connected in my Nuc.
+ i've two usb3 connected in my Nuc.
+ 
+ First : https://www.seagate.com/consumer/play/game-drive-xbox/#features
+ Second : 
https://maxtor.seagate.com/files/maxtor-content/homepage/content/pdf/DS1879_1_1512US_M3Portable.pdf
+ 
+ 
  I blacklistet with this option in /etc/modprobe.d/uas-ignore-usbexternal.conf 
:
  
  options usb-storage quirks=0bc2:2322,0bc2:61b7:u
  
  The only problem that only works on the second device :
  
  $ dmesg | grep Quirks
  [2.743539] usb-storage 2-3:1.0: Quirks match for vid 0bc2 pid 61b7: 80
  
  I tried with these kernels :
  
  - 4.15.023
  - 4.17.0
  - 4.17.1
  - 4.17.2
  - 4.18-rc1
  
- 
  Some info :
  
- $ sudo lsusb 
- Bus 002 Device 003: ID 0bc2:2322 Seagate RSS LLC 
- Bus 002 Device 002: ID 0bc2:61b7 Seagate RSS LLC 
+ $ sudo lsusb
+ Bus 002 Device 003: ID 0bc2:2322 Seagate RSS LLC
+ Bus 002 Device 002: ID 0bc2:61b7 Seagate RSS LLC
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
- Bus 001 Device 002: ID 20a0:0006 Clay Logic 
+ Bus 001 Device 002: ID 20a0:0006 Clay Logic
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  
- 
  I have attached DMESG and various logs

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

Title:
  USB-Storage Quirk for 0bc2:2322 and 0bc2:61b7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  i've two usb3 connected in my Nuc.

  First : https://www.seagate.com/consumer/play/game-drive-xbox/#features
  Second : 
https://maxtor.seagate.com/files/maxtor-content/homepage/content/pdf/DS1879_1_1512US_M3Portable.pdf

  
  I blacklistet with this option in /etc/modprobe.d/uas-ignore-usbexternal.conf 
:

  options usb-storage quirks=0bc2:2322,0bc2:61b7:u

  The only problem that only works on the second device :

  $ dmesg | grep Quirks
  [2.743539] usb-storage 2-3:1.0: Quirks match for vid 0bc2 pid 61b7: 80

  I tried with these kernels :

  - 4.15.023
  - 4.17.0
  - 4.17.1
  - 4.17.2
  - 4.18-rc1

  Some info :

  $ sudo lsusb
  Bus 002 Device 003: ID 0bc2:2322 Seagate RSS LLC
  Bus 002 Device 002: ID 0bc2:61b7 Seagate RSS LLC
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
  Bus 001 Device 002: ID 20a0:0006 Clay Logic
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I have attached DMESG and various logs

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

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

[Kernel-packages] [Bug 1777689] Re: USB-Storage Quirk for 0bc2:2322 and 0bc2:61b7

[Stefano]

** Attachment added: "udevadm_0bc2:2322"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777689/+attachment/5154341/+files/udevadm_0bc2_2322.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/1777689

Title:
  USB-Storage Quirk for 0bc2:2322 and 0bc2:61b7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  i've two usb3 connected in my Nuc.

  First : https://www.seagate.com/consumer/play/game-drive-xbox/#features
  Second : 
https://maxtor.seagate.com/files/maxtor-content/homepage/content/pdf/DS1879_1_1512US_M3Portable.pdf

  
  I blacklistet with this option in /etc/modprobe.d/uas-ignore-usbexternal.conf 
:

  options usb-storage quirks=0bc2:2322,0bc2:61b7:u

  The only problem that only works on the second device :

  $ dmesg | grep Quirks
  [2.743539] usb-storage 2-3:1.0: Quirks match for vid 0bc2 pid 61b7: 80

  I tried with these kernels :

  - 4.15.023
  - 4.17.0
  - 4.17.1
  - 4.17.2
  - 4.18-rc1

  Some info :

  $ sudo lsusb
  Bus 002 Device 003: ID 0bc2:2322 Seagate RSS LLC
  Bus 002 Device 002: ID 0bc2:61b7 Seagate RSS LLC
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
  Bus 001 Device 002: ID 20a0:0006 Clay Logic
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I have attached DMESG and various logs

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

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