[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04

2019-01-12 Thread Kai-Heng Feng
Seems like 4.15.0-43.46 is a CVE respin so the patch is not included.
Please wait for the next kernel release.

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

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

Bug description:
  ===SRU Justification===
  [Impact]
  Server console is extremely slow on ast, after the upgrade from 16.04 to
  18.04.

  [Fix]
  Remove firmware/bootloader configured framebuffer device before probing.

  [Test]
  User confirmed the patch fixes the issue.

  [Regression Potential]
  Low. The fix is in stable tree, limits to one specific device, and other
  DRM drivers already do this for a while.

  ===Original Bug Report===
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 15 07:22 seq
   crw-rw 1 root audio 116, 33 Dec 15 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: ASUSTeK COMPUTER INC. P9D-X Series
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9D-X Series
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: P9D-X Series
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

2019-01-12 Thread Daniel van Vugt
If the problem is that mentioned in comment #14 then indeed it will come
and go randomly.

Please finish following the steps in comment #14.

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.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.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4: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.sku: 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/1810861/+subscriptions

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


[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04

2019-01-12 Thread Daniel van Vugt
Mat,

This bug is about text console output only. Not the login screen or
graphical sessions.

Please log your own new bug by running:

   ubuntu-bug mutter

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

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

Bug description:
  ===SRU Justification===
  [Impact]
  Server console is extremely slow on ast, after the upgrade from 16.04 to
  18.04.

  [Fix]
  Remove firmware/bootloader configured framebuffer device before probing.

  [Test]
  User confirmed the patch fixes the issue.

  [Regression Potential]
  Low. The fix is in stable tree, limits to one specific device, and other
  DRM drivers already do this for a while.

  ===Original Bug Report===
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 15 07:22 seq
   crw-rw 1 root audio 116, 33 Dec 15 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: ASUSTeK COMPUTER INC. P9D-X Series
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9D-X Series
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: P9D-X Series
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04

2019-01-12 Thread Daniel van Vugt
Mat,

This bug is about text console output only. Not the login screen or
graphical sessions.

Please log your own new bug bug running:

   ubuntu-bug mutter

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

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

Bug description:
  ===SRU Justification===
  [Impact]
  Server console is extremely slow on ast, after the upgrade from 16.04 to
  18.04.

  [Fix]
  Remove firmware/bootloader configured framebuffer device before probing.

  [Test]
  User confirmed the patch fixes the issue.

  [Regression Potential]
  Low. The fix is in stable tree, limits to one specific device, and other
  DRM drivers already do this for a while.

  ===Original Bug Report===
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 15 07:22 seq
   crw-rw 1 root audio 116, 33 Dec 15 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: ASUSTeK COMPUTER INC. P9D-X Series
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9D-X Series
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: P9D-X Series
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1780131] Re: Blank screen on boot after latest upgrade

2019-01-12 Thread 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/1780131

Title:
  Blank screen on boot after latest upgrade

Status in ubuntu-mate:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm running Ubuntu MATE on the Entroware Triton, which uses Intel
  graphics.

  I've recently run the last set of updates (on 4th July 2018) and now
  when I boot up, I get a blank screen where the login screen should be.
  If I press the power button, the system shuts down cleanly.

  I can rectify the issue if I boot selecting the previous kernel from
  grub which is 4.15.0-23-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1780131/+subscriptions

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


[Kernel-packages] [Bug 1780009] Re: touchpad stops working after kernel update

2019-01-12 Thread 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/1780009

Title:
  touchpad stops working after kernel update

Status in linux package in Ubuntu:
  Expired

Bug description:
  My Asus touchpad stops working after the kernel update to 4.15.0-24. I
  had to revert to 4.15.0-23 to get the touchpad functionality back.
  External mice work just fine though. Another user reported not being
  able to get past the login screen on 4.15.0-24 as well. Here's the
  link of a post I made on the Ubuntu MATE Community.

  https://ubuntu-mate.community/t/asus-touchpad-not-working-after-
  kernel-update/17198

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

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


[Kernel-packages] [Bug 1780131] Re: Blank screen on boot after latest upgrade

2019-01-12 Thread Launchpad Bug Tracker
[Expired for ubuntu-mate because there has been no activity for 60
days.]

** Changed in: ubuntu-mate
   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/1780131

Title:
  Blank screen on boot after latest upgrade

Status in ubuntu-mate:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm running Ubuntu MATE on the Entroware Triton, which uses Intel
  graphics.

  I've recently run the last set of updates (on 4th July 2018) and now
  when I boot up, I get a blank screen where the login screen should be.
  If I press the power button, the system shuts down cleanly.

  I can rectify the issue if I boot selecting the previous kernel from
  grub which is 4.15.0-23-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1780131/+subscriptions

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


[Kernel-packages] [Bug 1800427] Re: sudo apt-get upgrade hangs

2019-01-12 Thread 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/1800427

Title:
  sudo apt-get upgrade hangs

Status in linux package in Ubuntu:
  Expired

Bug description:
  Installer Wine then did sudo apt-get update then sudo apt-get upgrade.

  Upgrade proceeded up to "Found initrd image:
  /boot/initrd.img-4.15.0-20-generic" then hung.

  While I waited a system error window popped up. I clicked send report.
  Then I got an error window stating that the error report asked for two
  things and only got 1. That the error report would not be sent.

  Below are the screen images of the terminal screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   robert 2158 F...m pulseaudio
   /dev/snd/controlC1:  robert 2158 F pulseaudio
   /dev/snd/controlC0:  robert 2158 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Oct 29 03:19:53 2018
  HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb
  InstallationDate: Installed on 2018-10-25 (4 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/1800427/+subscriptions

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


[Kernel-packages] [Bug 1803082] Re: linux: -proposed tracker

2019-01-12 Thread 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/1803082

Title:
  linux:  -proposed tracker

Status in linux package in Ubuntu:
  Expired

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

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

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

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


[Kernel-packages] [Bug 1690085]

2019-01-12 Thread eric.c.morgan
(In reply to dl9px from comment #468)
> Just asked the helpdesk what we can do to get help and more attention.
> Disabling c6 still is a workaround for me, but that's not how I intended to
> run my system.

Thanks.

I'm in the same boat with C6. I know I'm a small fish but my company
won't be using amd hardware until this is worked out.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel 

[Kernel-packages] [Bug 1690085]

2019-01-12 Thread dl9px
Just asked the helpdesk what we can do to get help and more attention.
Disabling c6 still is a workaround for me, but that's not how I intended
to run my system.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:

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

2019-01-12 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Immediate resume from suspend when wifi enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on a current and update 18.04.01 my 
  Acer TravelMate P648-M/BAD40_SL, BIOS V1.21 07/21/2017
  resumes immediately from suspend. 

  I can successfully enter suspend if I set laptop into flight mode.

  This symptom only appeared the last few days, 
  earlier the same system suspended just fine. 

  There are no differences in  /proc/acpi/wakeup 
  with and without flight mode.

  => What other debugging information would be needed 
 to figure what caused the resume with wifi enabled ?

  Yours, Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   sneumann   2816 F...m pulseaudio
   /dev/snd/controlC0:  sneumann   2816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 01:41:00 2019
  HibernationDevice: RESUME=UUID=045e8ed5-08d8-46a0-8ed4-606bd3be42a1
  InstallationDate: Installed on 2018-05-17 (240 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer TravelMate P648-M
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/lvmssd-bioinic ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BAD40_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd07/21/2017:svnAcer:pnTravelMateP648-M:pvrV1.21:rvnAcer:rnBAD40_SL:rvrV1.21:cvnAcer:ct10:cvrV1.21:
  dmi.product.family: SKL
  dmi.product.name: TravelMate P648-M
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1811545] Re: Immediate resume from suspend when wifi enabled

2019-01-12 Thread Steffen Neumann
Not sure if needed, but here is cat /proc/acpi/wakeup:

Device  S-state   Status   Sysfs node
PEGP  S4*disabled
PEG1  S4*disabled
PEGP  S4*disabled
PEG2  S4*disabled
PEGP  S4*disabled
GLAN  S4*enabled   pci::00:1f.6
XHC   S3*enabled   pci::00:14.0
XDCI  S4*disabled
HDAS  S4*disabled  pci::00:1f.3
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
RP05  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled  pci::01:00.0
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled  pci::3b:00.0
*disabled  platform:rtsx_pci_sdmmc.0
*disabled  platform:rtsx_pci_ms.0
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PXSX  S4*disabled
PWRB  S4*disabled

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

Title:
  Immediate resume from suspend when wifi enabled

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  on a current and update 18.04.01 my 
  Acer TravelMate P648-M/BAD40_SL, BIOS V1.21 07/21/2017
  resumes immediately from suspend. 

  I can successfully enter suspend if I set laptop into flight mode.

  This symptom only appeared the last few days, 
  earlier the same system suspended just fine. 

  There are no differences in  /proc/acpi/wakeup 
  with and without flight mode.

  => What other debugging information would be needed 
 to figure what caused the resume with wifi enabled ?

  Yours, Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   sneumann   2816 F...m pulseaudio
   /dev/snd/controlC0:  sneumann   2816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 01:41:00 2019
  HibernationDevice: RESUME=UUID=045e8ed5-08d8-46a0-8ed4-606bd3be42a1
  InstallationDate: Installed on 2018-05-17 (240 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer TravelMate P648-M
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/lvmssd-bioinic ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BAD40_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd07/21/2017:svnAcer:pnTravelMateP648-M:pvrV1.21:rvnAcer:rnBAD40_SL:rvrV1.21:cvnAcer:ct10:cvrV1.21:
  dmi.product.family: SKL
  dmi.product.name: TravelMate P648-M
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1811545] [NEW] Immediate resume from suspend when wifi enabled

2019-01-12 Thread Steffen Neumann
Public bug reported:

Hi,

on a current and update 18.04.01 my 
Acer TravelMate P648-M/BAD40_SL, BIOS V1.21 07/21/2017
resumes immediately from suspend. 

I can successfully enter suspend if I set laptop into flight mode.

This symptom only appeared the last few days, 
earlier the same system suspended just fine. 

There are no differences in  /proc/acpi/wakeup 
with and without flight mode.

=> What other debugging information would be needed 
   to figure what caused the resume with wifi enabled ?

Yours, Steffen

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   sneumann   2816 F...m pulseaudio
 /dev/snd/controlC0:  sneumann   2816 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 13 01:41:00 2019
HibernationDevice: RESUME=UUID=045e8ed5-08d8-46a0-8ed4-606bd3be42a1
InstallationDate: Installed on 2018-05-17 (240 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Acer TravelMate P648-M
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/lvmssd-bioinic ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware 1.173.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BAD40_SL
dmi.board.vendor: Acer
dmi.board.version: V1.21
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.21
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd07/21/2017:svnAcer:pnTravelMateP648-M:pvrV1.21:rvnAcer:rnBAD40_SL:rvrV1.21:cvnAcer:ct10:cvrV1.21:
dmi.product.family: SKL
dmi.product.name: TravelMate P648-M
dmi.product.version: V1.21
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug bionic

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

Title:
  Immediate resume from suspend when wifi enabled

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  on a current and update 18.04.01 my 
  Acer TravelMate P648-M/BAD40_SL, BIOS V1.21 07/21/2017
  resumes immediately from suspend. 

  I can successfully enter suspend if I set laptop into flight mode.

  This symptom only appeared the last few days, 
  earlier the same system suspended just fine. 

  There are no differences in  /proc/acpi/wakeup 
  with and without flight mode.

  => What other debugging information would be needed 
 to figure what caused the resume with wifi enabled ?

  Yours, Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   sneumann   2816 F...m pulseaudio
   /dev/snd/controlC0:  sneumann   2816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 01:41:00 2019
  HibernationDevice: RESUME=UUID=045e8ed5-08d8-46a0-8ed4-606bd3be42a1
  InstallationDate: Installed on 2018-05-17 (240 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer TravelMate P648-M
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/lvmssd-bioinic ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BAD40_SL
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd07/21/2017:svnAcer:pnTravelMateP648-M:pvrV1.21:rvnAcer:rnBAD40_SL:rvrV1.21:cvnAcer:ct10:cvrV1.21:
  dmi.product.family: SKL
  dmi.product.name: TravelMate P648-M
  dmi.product.version: V1.21
  dmi.sys.vendor: 

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

2019-01-12 Thread Dawid Olesinski
Linux Mint uses Ubuntu kernels so it won't work as I have tried newer
kernels as well (I'm on Ubuntu 18.04) I haven't tried Manjaro but I have
installed Arch free days ago and it didn't work. I guess I will have to
stick to that kernel 4.14-rc7 for some time. I might give it a go with
Manjaro tho.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  Hantick touchpad stops working after reboot.

  [Fix]
  Disable runtime power management for the touchpad.

  [Test]
  User confirmed it fixed the issue.
  Some users reported it doesn't work for them, I'll ask them to file new
  bugs for different touchpads.

  [Regression Potential]
  Low. Disable runtime power management doesn't affect devivce's
  funtionality. In general desktop usage the graphical session opens the
  touchpad HID device so the touchpad never get runtime suspended, so it
  won't hurt power in this case.

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

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

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

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

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

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


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

2019-01-12 Thread Brad
I don't know about LinuxMint but you can install Manjaro onto a USB
destination drive and boot from that to test it out first/without
touching your HDD/SD installation.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  Hantick touchpad stops working after reboot.

  [Fix]
  Disable runtime power management for the touchpad.

  [Test]
  User confirmed it fixed the issue.
  Some users reported it doesn't work for them, I'll ask them to file new
  bugs for different touchpads.

  [Regression Potential]
  Low. Disable runtime power management doesn't affect devivce's
  funtionality. In general desktop usage the graphical session opens the
  touchpad HID device so the touchpad never get runtime suspended, so it
  won't hurt power in this case.

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

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

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

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

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

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


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

2019-01-12 Thread Brad
Try Manjaro with kernel 4.19.xx or LinuxMint latest. There have been
various fixes for touchpad in newer kernels.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  Hantick touchpad stops working after reboot.

  [Fix]
  Disable runtime power management for the touchpad.

  [Test]
  User confirmed it fixed the issue.
  Some users reported it doesn't work for them, I'll ask them to file new
  bugs for different touchpads.

  [Regression Potential]
  Low. Disable runtime power management doesn't affect devivce's
  funtionality. In general desktop usage the graphical session opens the
  touchpad HID device so the touchpad never get runtime suspended, so it
  won't hurt power in this case.

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

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

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

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

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

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


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

2019-01-12 Thread Dawid Olesinski
EZBook 3 Pro v4 Touchpad stil not working. I've tried kernels from comment #187 
(v4.15.0-35) and comment #221 (v4.15.0-43.46) and both haven't worked. I have 
tried to reload modules for both kernels as well as suspending laptop. Nothing 
helps. 
Kernel v4.14-rc7 from comment #3 works correct apart from hard buttons. 

dmidecode -s bios-version
JUMPER2x.P8.WP313R.NHNAUHN05
dmidecode -s bios-release-date
09/30/2017
[6.410333] hid-multitouch 0018:0911:5288.0003: input,hidraw2: I2C HID v1.00 
Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  Hantick touchpad stops working after reboot.

  [Fix]
  Disable runtime power management for the touchpad.

  [Test]
  User confirmed it fixed the issue.
  Some users reported it doesn't work for them, I'll ask them to file new
  bugs for different touchpads.

  [Regression Potential]
  Low. Disable runtime power management doesn't affect devivce's
  funtionality. In general desktop usage the graphical session opens the
  touchpad HID device so the touchpad never get runtime suspended, so it
  won't hurt power in this case.

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

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

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

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

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

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


[Kernel-packages] [Bug 564376] Re: Lucid - radeon kms causes iwl3945 to drop connection on youtube but not with mainline

2019-01-12 Thread Christopher M. Penalver
** No longer affects: linux (Ubuntu)

** Project changed: xserver-xorg-driver-ati => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: freedesktop.org Bugzilla #28106 => None

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

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

Title:
  Lucid - radeon kms causes iwl3945 to drop connection on youtube but
  not with mainline

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Forgive me if this bug is a duplicate but I didn't see a recent bug
  with these details I did a clean install of Kubuntu 10.04 beta 2
  and i noticed the wireless connection would work initially after boot
  and then it would drop and then tray icon would continue to say
  "Connecting" and "Activating" when i right clicked on it and never
  connect again. I did get it to reconnect once after unloading the
  iwl3945 and iwlcore modules and reloading them, then restarting the
  networking init.d script, but that only worked once, every other time
  i had to reboot for it to work again. Most recently though i connected
  it and left it on overnight and it stayed connected fine the whole
  time (i had received IMs meanwhile) and i was able to browse through
  gmail and the web fine but as soon as I went to a YouTube link it
  died right away. So then i installed the mainline kernel version:
  2.6.34-999 from  http://kernel.ubuntu.com/~kernel-
  ppa/mainline/daily/current/ and tried the same YouTube link and
  everything works fine.

  Previous kernel versions I was using that had the problem:
  2.6.32-19
  2.6.32-21

  By the way in case it matters I was using google chrome as the browser and 
the wireless network I am connected too is using DD-WRT v24-sp1with WPA 
Personal. My laptop is an IBM Thinkpad T60 and here is my lspci:
  00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express Memory Controller Hub (rev 03)
  00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express PCI Express Root Port (rev 03)
  00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition 
Audio Controller (rev 02)
  00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 
(rev 02)
  00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 
(rev 02)
  00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 
(rev 02)
  00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 
(rev 02)
  00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controller 
#1 (rev 02)
  00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #2 (rev 02)
  00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #3 (rev 02)
  00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #4 (rev 02)
  00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI 
Controller (rev 02)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
  00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge 
(rev 02)
  00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller 
(rev 02)
  00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA 
AHCI Controller (rev 02)
  00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
  01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility Radeon 
X1300]
  02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet 
Controller
  03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller

   $ lsmod | grep iw
  iwl394575395  0
  iwlcore   118803  1 iwl3945
  mac80211  229304  2 iwl3945,iwlcore
  cfg80211  148737  3 iwl3945,iwlcore,mac80211

  So for now it seems to be working fine with the mainline kernel I installed 
but if there is any other info/testing i can provide let me know.
  Thanks,
  Nick

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

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


[Kernel-packages] [Bug 564376] [NEW] Lucid - radeon kms causes iwl3945 to drop connection on youtube but not with mainline

2019-01-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Forgive me if this bug is a duplicate but I didn't see a recent bug with
these details I did a clean install of Kubuntu 10.04 beta 2 and i
noticed the wireless connection would work initially after boot and then
it would drop and then tray icon would continue to say "Connecting" and
"Activating" when i right clicked on it and never connect again. I did
get it to reconnect once after unloading the iwl3945 and iwlcore modules
and reloading them, then restarting the networking init.d script, but
that only worked once, every other time i had to reboot for it to work
again. Most recently though i connected it and left it on overnight and
it stayed connected fine the whole time (i had received IMs meanwhile)
and i was able to browse through gmail and the web fine but as soon as I
went to a YouTube link it  died right away. So then i installed the
mainline kernel version: 2.6.34-999 from  http://kernel.ubuntu.com
/~kernel-ppa/mainline/daily/current/ and tried the same YouTube link and
everything works fine.

Previous kernel versions I was using that had the problem:
2.6.32-19
2.6.32-21

By the way in case it matters I was using google chrome as the browser and the 
wireless network I am connected too is using DD-WRT v24-sp1with WPA Personal. 
My laptop is an IBM Thinkpad T60 and here is my lspci:
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT 
Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio 
Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 
02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 
02)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 
02)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 
02)
00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controller 
#1 (rev 02)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller 
#2 (rev 02)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller 
#3 (rev 02)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller 
#4 (rev 02)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller 
(rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge 
(rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller 
(rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI 
Controller (rev 02)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility Radeon 
X1300]
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet 
Controller
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller

 $ lsmod | grep iw
iwl394575395  0
iwlcore   118803  1 iwl3945
mac80211  229304  2 iwl3945,iwlcore
cfg80211  148737  3 iwl3945,iwlcore,mac80211

So for now it seems to be working fine with the mainline kernel I installed but 
if there is any other info/testing i can provide let me know.
Thanks,
Nick

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


** Tags: apport-collected kj-triage lucid
-- 
Lucid - radeon kms causes iwl3945 to drop connection on youtube but not with 
mainline
https://bugs.launchpad.net/bugs/564376
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1805195] Re: linux: 4.19.0-6.7 -proposed tracker

2019-01-12 Thread Seth Forshee
*** This bug is a duplicate of bug 1811452 ***
https://bugs.launchpad.net/bugs/1811452

** This bug is no longer a duplicate of bug 1806952
   linux: 4.19.0-8.9 -proposed tracker
** This bug has been marked a duplicate of bug 1811452
   linux: 4.19.0-10.11 -proposed tracker

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

Title:
  linux: 4.19.0-6.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

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

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

  backports: 
  derivatives:
  -- swm properties --
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded
promote-to-release: Testing not complete

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

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


[Kernel-packages] [Bug 1806952] Re: linux: 4.19.0-8.9 -proposed tracker

2019-01-12 Thread Seth Forshee
*** This bug is a duplicate of bug 1811452 ***
https://bugs.launchpad.net/bugs/1811452

** This bug has been marked a duplicate of bug 1811452
   linux: 4.19.0-10.11 -proposed tracker

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

Title:
  linux: 4.19.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

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

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

  backports: 
  derivatives:
  -- swm properties --
  phase: Testing -- automated-testing in progress
  phase-changed: Wednesday, 09. January 2019 14:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1805465] Re: linux: 4.19.0-7.8 -proposed tracker

2019-01-12 Thread Seth Forshee
*** This bug is a duplicate of bug 1811452 ***
https://bugs.launchpad.net/bugs/1811452

** This bug is no longer a duplicate of bug 1806952
   linux: 4.19.0-8.9 -proposed tracker
** This bug has been marked a duplicate of bug 1811452
   linux: 4.19.0-10.11 -proposed tracker

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

Title:
  linux: 4.19.0-7.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

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

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

  backports: 
  derivatives:
  -- swm properties --
  phase: Promoted to proposed
  phase-changed: Friday, 30. November 2018 15:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress

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

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


[Kernel-packages] [Bug 1810297] Re: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107

2019-01-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package nvidia-utils-390 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in
  package nvidia-340 340.107-0ubuntu0.18.04.1

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

Bug description:
  Problem occured while going through these steps
  https://medium.com/@taylordenouden/installing-tensorflow-gpu-on-
  ubuntu-18-04-89a142325138

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-utils-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jan  2 18:27:00 2019
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-340 340.107-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-12-31 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-utils-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
  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/1810297/+subscriptions

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


[Kernel-packages] [Bug 564376]

2019-01-12 Thread mirh
Many of the linked issues report the problem fixed (broadly, by the time
of ubuntu 14.04).

Is this still a thing?

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

Title:
  Lucid - radeon kms causes iwl3945 to drop connection on youtube but
  not with mainline

Status in xserver-xorg-driver-ati:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Forgive me if this bug is a duplicate but I didn't see a recent bug
  with these details I did a clean install of Kubuntu 10.04 beta 2
  and i noticed the wireless connection would work initially after boot
  and then it would drop and then tray icon would continue to say
  "Connecting" and "Activating" when i right clicked on it and never
  connect again. I did get it to reconnect once after unloading the
  iwl3945 and iwlcore modules and reloading them, then restarting the
  networking init.d script, but that only worked once, every other time
  i had to reboot for it to work again. Most recently though i connected
  it and left it on overnight and it stayed connected fine the whole
  time (i had received IMs meanwhile) and i was able to browse through
  gmail and the web fine but as soon as I went to a YouTube link it
  died right away. So then i installed the mainline kernel version:
  2.6.34-999 from  http://kernel.ubuntu.com/~kernel-
  ppa/mainline/daily/current/ and tried the same YouTube link and
  everything works fine.

  Previous kernel versions I was using that had the problem:
  2.6.32-19
  2.6.32-21

  By the way in case it matters I was using google chrome as the browser and 
the wireless network I am connected too is using DD-WRT v24-sp1with WPA 
Personal. My laptop is an IBM Thinkpad T60 and here is my lspci:
  00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express Memory Controller Hub (rev 03)
  00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 
945GT Express PCI Express Root Port (rev 03)
  00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition 
Audio Controller (rev 02)
  00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 
(rev 02)
  00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 
(rev 02)
  00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 
(rev 02)
  00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 
(rev 02)
  00:1d.0 USB Controller: Intel Corporation N10/ICH7 Family USB UHCI Controller 
#1 (rev 02)
  00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #2 (rev 02)
  00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #3 (rev 02)
  00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI 
Controller #4 (rev 02)
  00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI 
Controller (rev 02)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
  00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge 
(rev 02)
  00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller 
(rev 02)
  00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA 
AHCI Controller (rev 02)
  00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
  01:00.0 VGA compatible controller: ATI Technologies Inc M52 [Mobility Radeon 
X1300]
  02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet 
Controller
  03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  15:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller

   $ lsmod | grep iw
  iwl394575395  0
  iwlcore   118803  1 iwl3945
  mac80211  229304  2 iwl3945,iwlcore
  cfg80211  148737  3 iwl3945,iwlcore,mac80211

  So for now it seems to be working fine with the mainline kernel I installed 
but if there is any other info/testing i can provide let me know.
  Thanks,
  Nick

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/564376/+subscriptions

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


[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04

2019-01-12 Thread Mat Nightingale
I've just done a clean install of 18.04 and have the same issue where
running 18.04 off a boot usb stick works flawlessly, however after
installing on the hard drive the login screen is very laggy and once I
enter my password the screen resolution is all messed up and unreadable.

If I reboot and hold down shift to get the Grub menu and choose Advanced
then recovery mode and then without altering anything I choose resume
from the recovery menu and the login screen works perfectly.

So I assume the fix hasn't been rolled out yet as I've run the updater
and there's nothing that needs updating on my system.

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

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

Bug description:
  ===SRU Justification===
  [Impact]
  Server console is extremely slow on ast, after the upgrade from 16.04 to
  18.04.

  [Fix]
  Remove firmware/bootloader configured framebuffer device before probing.

  [Test]
  User confirmed the patch fixes the issue.

  [Regression Potential]
  Low. The fix is in stable tree, limits to one specific device, and other
  DRM drivers already do this for a while.

  ===Original Bug Report===
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 15 07:22 seq
   crw-rw 1 root audio 116, 33 Dec 15 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: ASUSTeK COMPUTER INC. P9D-X Series
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9D-X Series
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: P9D-X Series
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-01-12 Thread Christopher M. Penalver
Eugene Kosogin, here are some ways to engage ASUS on this particular
issue:

1) Advise support the issue is reproduced using Windows 10 x64 (OS precisely 
quoted from the ASUS website below) so Consumer Support can't disclaim 
responsibility. You will likely get the best traction with them if this is the 
case:
https://www.asus.com/us/ROG-Republic-Of-Gamers/ROG-G752VT/HelpDesk_Download/

2) Reach out to someone at their Corporate HQ regarding a BIOS fix request:
https://www.asus.com/us/About_ASUS/Facilities-Branches/

3) Contact ASUS Security. Given the BIOS appears to behave improperly, one 
could see how hackers would investigate this for BIOS exploitation:
https://www.asus.com/Static_WebPage/ASUS-Product-Security-Advisory/

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

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

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor 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 audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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


[Kernel-packages] [Bug 1089768] Re: When IOMMU enabled, devices attached to Marvell 88SE9128 controller not recognized

2019-01-12 Thread Christopher M. Penalver
Steven Ellis (steven-openmedia), it will help immensely if you use the computer 
the problem is reproducible with to provide necessary debugging logs by filing 
a new report in Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Summary changed:

- Marvell Sata controller and AMD-Vi problems
+ When IOMMU enabled, devices attached to Marvell 88SE9128 controller not 
recognized

** Tags added: bios-outdated-f3

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

Title:
  When IOMMU enabled, devices attached to Marvell 88SE9128 controller
  not recognized

Status in linux package in Ubuntu:
  Expired

Bug description:
  This bug is to confirm that the Marvell 88SE9128 chipset bug presents
  under AMD's IOMMU implementation as well as Intel's VT-D. I've tested
  this with a Syba SD-PEX40035 and a Highpoint Rocket 620 (both use the
  same Marvell chipset) PCIe card, under both the stock Quantal kernel
  and the 3.7.0rc8 kernel from the mainline kernel PPA. It sounds like
  the preferred solution is PCI quirk, and some of the infrastructure is
  in place, but it hasn't been implemented yet. Symptoms consist of a
  much longer boot process, and failure to identify any devices attached
  to the Marvell controllers.

  WORKAROUND: Works fine as long as I disable the IOMMU in the BIOS.

  My system consists of an AMD A10-5800K in a Gigabyte GA-F2A85X-D3H
  motherboard, 5x Seagate 1.5 TB drives in software Raid5, 4x Seagate 3
  TB drives in a native ZFS raidz (not yet used), a Sata BD-ROM, and a
  500 GB sata drive (not yet used).

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005226
  http://lists.linuxfoundation.org/pipermail/iommu/2012-September/004551.html
  https://bugzilla.kernel.org/show_bug.cgi?id=42679
  https://bugzilla.redhat.com/show_bug.cgi?id=757166

  pci 02:00.1 is the IDE endpoint, but there are no PATA devices in the
  system, which matches the behavior of the other chips (emitting DMA
  operations from the wrong PCI endpoint, which the IOMMU rejects.)

  ##
  02:00.1 IDE interface: Marvell Technology Group Ltd. 88SE9128 IDE Controller 
(rev 11) (prog-if 8f [Master SecP SecO PriP PriO])
  Subsystem: Marvell Technology Group Ltd. 88SE9128 IDE Controller
  Flags: bus master, fast devsel, latency 0, IRQ 18
  I/O ports at d040 [size=8]
  I/O ports at d030 [size=4]
  I/O ports at d020 [size=8]
  I/O ports at d010 [size=4]
  I/O ports at d000 [size=16]
  Memory at fea2 (32-bit, non-prefetchable) [size=16]
  Expansion ROM at fea0 [disabled] [size=64K]
  Capabilities: [40] Power Management version 3
  Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
  Capabilities: [70] Express Legacy Endpoint, MSI 00
  Capabilities: [100] Advanced Error Reporting
  Kernel driver in use: pata_marvell
  Kernel modules: pata_marvell

  ##
  [1.225703] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.1 
domain=0x001d address=0x001003c0 flags=0x]
  
  [6.207818] ata16.00: qc timeout (cmd 0xa1)
  [6.215674] ata9.00: qc timeout (cmd 0xa1)
  [6.215681] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.223640] ata24.00: qc timeout (cmd 0xa1)
  [6.231606] ata17.00: qc timeout (cmd 0xec)
  [6.231627] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.239574] ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.343207] ata18.00: qc timeout (cmd 0xec)
  [6.351204] ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.534578] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.558489] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.709935] ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [7.531002] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [   11.588451] ata17: link is slow to respond, please be patient (ready=0)
  [   11.700054] ata18: link is slow to respond, please be patient (ready=0)
  [   16.219859] ata17: COMRESET failed (errno=-16)
  [   16.331454] ata18: COMRESET failed (errno=-16)
  [   16.498853] ata9.00: qc timeout (cmd 0xa1)
  [   16.498865] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [   16.498870] ata9: limiting SATA link speed to 1.5 Gbps
  [   16.522792] ata24.00: qc timeout (cmd 0xa1)
  [   16.522804] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [   16.522807] ata24: limiting SATA link speed to 1.5 Gbps
  [   16.817725] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   16.849613] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   17.495260] ata16.00: qc timeout (cmd 0xa1)
  [   17.997499] ata16.00: failed to IDENTIFY (I/O error, 

[Kernel-packages] [Bug 1089768] Re: Marvell Sata controller and AMD-Vi problems

2019-01-12 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Importance: Medium => Low

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

Title:
  When IOMMU enabled, devices attached to Marvell 88SE9128 controller
  not recognized

Status in linux package in Ubuntu:
  Expired

Bug description:
  This bug is to confirm that the Marvell 88SE9128 chipset bug presents
  under AMD's IOMMU implementation as well as Intel's VT-D. I've tested
  this with a Syba SD-PEX40035 and a Highpoint Rocket 620 (both use the
  same Marvell chipset) PCIe card, under both the stock Quantal kernel
  and the 3.7.0rc8 kernel from the mainline kernel PPA. It sounds like
  the preferred solution is PCI quirk, and some of the infrastructure is
  in place, but it hasn't been implemented yet. Symptoms consist of a
  much longer boot process, and failure to identify any devices attached
  to the Marvell controllers.

  WORKAROUND: Works fine as long as I disable the IOMMU in the BIOS.

  My system consists of an AMD A10-5800K in a Gigabyte GA-F2A85X-D3H
  motherboard, 5x Seagate 1.5 TB drives in software Raid5, 4x Seagate 3
  TB drives in a native ZFS raidz (not yet used), a Sata BD-ROM, and a
  500 GB sata drive (not yet used).

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005226
  http://lists.linuxfoundation.org/pipermail/iommu/2012-September/004551.html
  https://bugzilla.kernel.org/show_bug.cgi?id=42679
  https://bugzilla.redhat.com/show_bug.cgi?id=757166

  pci 02:00.1 is the IDE endpoint, but there are no PATA devices in the
  system, which matches the behavior of the other chips (emitting DMA
  operations from the wrong PCI endpoint, which the IOMMU rejects.)

  ##
  02:00.1 IDE interface: Marvell Technology Group Ltd. 88SE9128 IDE Controller 
(rev 11) (prog-if 8f [Master SecP SecO PriP PriO])
  Subsystem: Marvell Technology Group Ltd. 88SE9128 IDE Controller
  Flags: bus master, fast devsel, latency 0, IRQ 18
  I/O ports at d040 [size=8]
  I/O ports at d030 [size=4]
  I/O ports at d020 [size=8]
  I/O ports at d010 [size=4]
  I/O ports at d000 [size=16]
  Memory at fea2 (32-bit, non-prefetchable) [size=16]
  Expansion ROM at fea0 [disabled] [size=64K]
  Capabilities: [40] Power Management version 3
  Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
  Capabilities: [70] Express Legacy Endpoint, MSI 00
  Capabilities: [100] Advanced Error Reporting
  Kernel driver in use: pata_marvell
  Kernel modules: pata_marvell

  ##
  [1.225703] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.1 
domain=0x001d address=0x001003c0 flags=0x]
  
  [6.207818] ata16.00: qc timeout (cmd 0xa1)
  [6.215674] ata9.00: qc timeout (cmd 0xa1)
  [6.215681] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.223640] ata24.00: qc timeout (cmd 0xa1)
  [6.231606] ata17.00: qc timeout (cmd 0xec)
  [6.231627] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.239574] ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.343207] ata18.00: qc timeout (cmd 0xec)
  [6.351204] ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [6.534578] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.558489] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.709935] ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [7.531002] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [   11.588451] ata17: link is slow to respond, please be patient (ready=0)
  [   11.700054] ata18: link is slow to respond, please be patient (ready=0)
  [   16.219859] ata17: COMRESET failed (errno=-16)
  [   16.331454] ata18: COMRESET failed (errno=-16)
  [   16.498853] ata9.00: qc timeout (cmd 0xa1)
  [   16.498865] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [   16.498870] ata9: limiting SATA link speed to 1.5 Gbps
  [   16.522792] ata24.00: qc timeout (cmd 0xa1)
  [   16.522804] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [   16.522807] ata24: limiting SATA link speed to 1.5 Gbps
  [   16.817725] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   16.849613] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   17.495260] ata16.00: qc timeout (cmd 0xa1)
  [   17.997499] ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4)
  [   17.997504] ata16: limiting SATA link speed to 1.5 Gbps
  [   18.818556] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   21.568700] ata17: link is slow to respond, please be patient (ready=0)
  [   21.680300] ata18: link is slow to respond, please be patient (ready=0)
  [   26.200104] ata17: COMRESET failed (errno=-16)
  [   26.311693] ata18: COMRESET 

[Kernel-packages] [Bug 571770] Re: Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling

2019-01-12 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Importance: High => Undecided

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

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

Title:
  Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: linux-image-2.6.32-22-generic

  Sometimes during audio playback, a kernel thread named "[hd-audio0]"
  will consume excessive amounts of CPU and cause  audio crackling. It
  seems to be more easily triggered when displaying video in fullscreen
  (or Rhythmbox visualizations) or dragging windows around while playing
  music, somehow relating it graphics operations (running default radeon
  driver with KMS and Compiz).

  This all started after moving from Ubuntu Karmic to Lucid (never had
  this problem before).

  Setting package to kernel, since it's probably alsa snd_hda_intel
  kernel module which is to blame.

  Ubuntu 10.04 x86, Intel Core Duo 2GHz, 3GB RAM, ATI X1400 Radeon Mobility 
graphics.
  Audio chip: Analog Devices AD1981 [HDA]

  WORKAROUND: Disabling radeon KMS makes all the audio crackling go
  away.

  Attaching:
  * Screenshot of top running over Rhythmbox w/fullscreen visualizations, 
showing [hd-audio0] consuming more CPU than everything else at the time (audio 
crackles).
  * Output of "lspci -vvnn"
  * Output of "dmesg"
  * Contents of /proc/interrupts
  * ALSA info, as provided by the alsa-info.sh script.

  Related to this: https://bugzilla.kernel.org/show_bug.cgi?id=14935 ???

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

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


[Kernel-packages] [Bug 1811512] Re: package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

2019-01-12 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub
  exited with return code 127

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I haw a dell latitude d630 and the start-up proses is 5 min after
  upgrading to this ubuntu version.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_39_42_generic_46
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1113 F pulseaudio
kjell  1892 F pulseaudio
  Date: Sat Jan 12 12:22:57 2019
  DuplicateSignature:
   package:linux-image-4.15.0-42-generic:4.15.0-42.45
   Setting up grub-pc (2.02-2ubuntu8.9) ...
   /var/lib/dpkg/info/grub-pc.config: 14: /etc/default/grub: ESC: not found
   dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned 
error exit status 127
  ErrorMessage: installed linux-image-4.15.0-42-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2016-05-01 (985 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=c00e298c-c98c-4a35-bbb9-d58b14d15155 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.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/01/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1811512] [NEW] package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

2019-01-12 Thread Kjell Engström
Public bug reported:

I haw a dell latitude d630 and the start-up proses is 5 min after
upgrading to this ubuntu version.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-42-generic 4.15.0-42.45
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_39_42_generic_46
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1113 F pulseaudio
  kjell  1892 F pulseaudio
Date: Sat Jan 12 12:22:57 2019
DuplicateSignature:
 package:linux-image-4.15.0-42-generic:4.15.0-42.45
 Setting up grub-pc (2.02-2ubuntu8.9) ...
 /var/lib/dpkg/info/grub-pc.config: 14: /etc/default/grub: ESC: not found
 dpkg: error processing package grub-pc (--configure):
  installed grub-pc package post-installation script subprocess returned error 
exit status 127
ErrorMessage: installed linux-image-4.15.0-42-generic package post-installation 
script subprocess returned error exit status 1
InstallationDate: Installed on 2016-05-01 (985 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Latitude D630
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=c00e298c-c98c-4a35-bbb9-d58b14d15155 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.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
SourcePackage: linux-signed
Title: package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 127
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0KU184
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/01/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D630
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub
  exited with return code 127

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I haw a dell latitude d630 and the start-up proses is 5 min after
  upgrading to this ubuntu version.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_39_42_generic_46
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1113 F pulseaudio
kjell  1892 F pulseaudio
  Date: Sat Jan 12 12:22:57 2019
  DuplicateSignature:
   package:linux-image-4.15.0-42-generic:4.15.0-42.45
   Setting up grub-pc (2.02-2ubuntu8.9) ...
   /var/lib/dpkg/info/grub-pc.config: 14: /etc/default/grub: ESC: not found
   dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned 
error exit status 127
  ErrorMessage: installed linux-image-4.15.0-42-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2016-05-01 (985 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=c00e298c-c98c-4a35-bbb9-d58b14d15155 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.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-42-generic 4.15.0-42.45 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 127
  

[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-12 Thread Kai-Heng Feng
@cking,

The PR is now merged, please backport it to Ubuntu's thermald.

Thanks!

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

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

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