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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

Title:
  BUG: unable to handle kernel paging request at 0b570057

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to play music using Rhytmbox

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20 [modified: 
boot/vmlinuz-4.13.0-17-generic]
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 904 F pulseaudio
bertadmin   1272 F pulseaudio
  Date: Tue Dec 26 02:51:29 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: VbglR0PhysHeapFree+0xb5/0x160 [vboxguest] RSP: 9c9482813ba8
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 0b570057
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1740225] Re: BUG: unable to handle kernel paging request at 00000b5700000057

[Ubuntu Kernel 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/1740225

Title:
  BUG: unable to handle kernel paging request at 0b570057

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to play music using Rhytmbox

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20 [modified: 
boot/vmlinuz-4.13.0-17-generic]
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 904 F pulseaudio
bertadmin   1272 F pulseaudio
  Date: Tue Dec 26 02:51:29 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: VbglR0PhysHeapFree+0xb5/0x160 [vboxguest] RSP: 9c9482813ba8
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 0b570057
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1740225] Re: BUG: unable to handle kernel paging request at 00000b5700000057

[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 in Ubuntu.
https://bugs.launchpad.net/bugs/1740225

Title:
  BUG: unable to handle kernel paging request at 0b570057

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to play music using Rhytmbox

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20 [modified: 
boot/vmlinuz-4.13.0-17-generic]
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 904 F pulseaudio
bertadmin   1272 F pulseaudio
  Date: Tue Dec 26 02:51:29 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: VbglR0PhysHeapFree+0xb5/0x160 [vboxguest] RSP: 9c9482813ba8
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 0b570057
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1740225] [NEW] BUG: unable to handle kernel paging request at 00000b5700000057

[BertN45]

Public bug reported:

Trying to play music using Rhytmbox

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-17-generic 4.13.0-17.20 [modified: 
boot/vmlinuz-4.13.0-17-generic]
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 904 F pulseaudio
  bertadmin   1272 F pulseaudio
Date: Tue Dec 26 02:51:29 2017
DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: VbglR0PhysHeapFree+0xb5/0x160 [vboxguest] RSP: 9c9482813ba8
Failure: oops
InstallationDate: Installed on 2017-12-22 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
IwConfig:
 enp0s3no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 0b570057
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-kerneloops bionic kernel-driver-vboxguest kernel-oops

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

Title:
  BUG: unable to handle kernel paging request at 0b570057

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to play music using Rhytmbox

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20 [modified: 
boot/vmlinuz-4.13.0-17-generic]
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 904 F pulseaudio
bertadmin   1272 F pulseaudio
  Date: Tue Dec 26 02:51:29 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: VbglR0PhysHeapFree+0xb5/0x160 [vboxguest] RSP: 9c9482813ba8
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel paging request at 0b570057
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  

[Kernel-packages] [Bug 1734147] Re: Your mail to sid...@brownstwnhouse.org

[lucy PAHASTA]

Steve is sorry to inform you thaty this mailbox has, most likely, been
redflagged by agencies in charge of our security.  Text him, instead --
2063057170.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Prasanna]

Finally, I got it fixed today this way...
https://askubuntu.com/questions/984043/unable-to-make-changes-in-bios-after-17-10-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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[lucy PAHASTA]

Add Lenovo G560 to this list, as mine was borked online, too.  
Firtst, no cdrom, then no boot from live usb, then  .  .  .  no BIOS access.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1634593] Re: Elantech Touchpad detects as PS/2 BYD TouchPad or as a PS/2 generic mouse

[Damien Boyd]

over 1 year after last comment... behavior still exists.

ash@CASE:~$ uname -a
Linux CASE 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
ash@CASE:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

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

Title:
  Elantech Touchpad detects as PS/2 BYD TouchPad or as a PS/2 generic
  mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Elantech Touchpad installed on my Lenovo Y700 laptop and I
  can't make it work properly by any means. I tried to switch between
  libinput and synaptics but this bug seems to affect any driver.

  Usually, after a system upgrade all works properly till the moment I
  plug in external mouse (Razer DeathAdder 3500DPI). After that touchpad
  detected as either PS/2 BYD or PS/2 generic mouse or sometimes PS/2
  Elantech touchpad.

  After some 5-6 reboots without plugging in external mouse the touchpad
  finally starts to detect it as ETPS/2 Elantech touchpad.

  Reloading psmouse module seems to cause no effect (or it does yet
  after a minute touchpad stops working for a moment and then switches
  to PS/2 in xinput). Multitouch stops working as well as tapping with
  two fingers.

  I tried almost all the possible workarounds involving adding boot
  options, installing elantech driver fixes etc.

  Help is appreciated.

  The output of xinput as for now:

  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PS/2 BYD TouchPad   id=14   [slave  pointer 
 (2)]

  lsinput
  /dev/input/event14
     bustype : BUS_I8042
     vendor  : 0x2
     product : 0x1
     version : 99
     name: "PS/2 BYD TouchPad"
     phys: "isa0060/serio1/input0"
     bits ev : EV_SYN EV_KEY EV_REL

  UPDATE:

  Seems that forcing the psmouse to detect the touchpad as elantech
  helps to fix problem temporarily. But it works only from time to time:

  $ sudo rmmod psmouse
  $ sudo modprobe psmouse force="elantech"
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-08-27 (52 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.6.0-040600-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Andrey]

Hi.
Have checked yesterday evening once again.
So - Lenovo E31-70 Xubuntu 16.04.03, kernel 4.14.8 (installed with ukuu) - bios 
settings survive reboot, secure boot can be disabled. I created bootable usb 
with Linux Mint - it is recognized in bios and boot from it.

So that is it.

PS It was really pain in the .ss, started in May when I've found this 
problem.
PSS Poor support from Lenovo and  Insyde - at least in my case.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Laptop does not suspend (instead, it shuts down) when lid is closed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a recent kernel update, when I close my laptop lid, instead of
  suspending, my laptop shuts down.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 18:57:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=fc36807e-e60f-4bbf-82f0-e9db1e6e967a ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-07 (49 days ago)
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.10
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.10:bd10/12/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1740197] [NEW] Laptop does not suspend (instead, it shuts down) when lid is closed

[Raffi Khatchadourian]

Public bug reported:

After a recent kernel update, when I close my laptop lid, instead of
suspending, my laptop shuts down.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-21-generic 4.13.0-21.24
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 26 18:57:53 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=fc36807e-e60f-4bbf-82f0-e9db1e6e967a ro quiet splash vt.handoff=7
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-11-07 (49 days ago)
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.10
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.10:bd10/12/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Laptop does not suspend (instead, it shuts down) when lid is closed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a recent kernel update, when I close my laptop lid, instead of
  suspending, my laptop shuts down.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 18:57:53 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=fc36807e-e60f-4bbf-82f0-e9db1e6e967a ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-07 (49 days ago)
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.10
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.10:bd10/12/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1574130] Re: radeon GPU lockup when using VLC and Firefox

[Hey!]

Hi.

I'm having this issue on Elementary and Xubuntu with the same card
(HD6870), but Firefox doesn't need to be running.

Unity and Gnome apparently fixed the issue since vlc works really well.

Does anybody know where could be the issue on Elementary.

Setting the radeon.dpm=0 makes the problem go away, but i don't feel
comfortable using it since it must put a lot of stress on the card.

I'm using kernel 4.10 with the 16.04 hwe stack on all the distro's and
only Unity and Gnome work out of the box.

Thanks.

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

Title:
  radeon GPU lockup when using VLC and Firefox

Status in linux package in Ubuntu:
  Expired

Bug description:
  When playing a video with VLC and running Firefox at the same time,
  the radeon driver consistently (reproducibly) locks up and crashes on
  my machine since upgrading to 16.04. I'm using a Radeon HD 6870.

  This does not happen with other video players (totem, mpv). Tested
  with different video codecs and different window managers (gnome-
  shell, metacity).

  When VLC starts, the following message is printed to dmesg:

  [  102.379520] [drm:btc_dpm_set_power_state [radeon]] *ERROR*
  rv770_restrict_performance_levels_before_switch failed

  This is not the case with Totem.
  When Firefox is started, or if Firefox had been running in the first place, a 
few seconds later it locks up:

  [  157.157196] radeon :01:00.0: ring 5 stalled for more than 10104msec
  [  157.157212] radeon :01:00.0: GPU lockup (current fence id 
0x03b7 last fence id 0x03bb on ring 5)
  [  157.506657] radeon :01:00.0: couldn't schedule ib
  [  157.506746] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD 
(-22)!
  [  157.507820] radeon :01:00.0: Saved 535 dwords of commands on ring 0.
  [  157.507840] radeon :01:00.0: GPU softreset: 0x0088
  [  157.507846] radeon :01:00.0:   GRBM_STATUS   = 0xA0003828
  [  157.507852] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
  [  157.507858] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
  [  157.507863] radeon :01:00.0:   SRBM_STATUS   = 0x200040C0
  [  157.507868] radeon :01:00.0:   SRBM_STATUS2  = 0x
  [  157.507874] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x
  [  157.507879] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x0001
  [  157.507884] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x0002
  [  157.507890] radeon :01:00.0:   R_008680_CP_STAT  = 0x80010243
  [  157.507895] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
  [  157.520474] radeon :01:00.0: GRBM_SOFT_RESET=0x4001
  [  157.520532] radeon :01:00.0: SRBM_SOFT_RESET=0x8100
  [  157.521682] radeon :01:00.0:   GRBM_STATUS   = 0x3828
  [  157.521687] radeon :01:00.0:   GRBM_STATUS_SE0   = 0x0007
  [  157.521692] radeon :01:00.0:   GRBM_STATUS_SE1   = 0x0007
  [  157.521698] radeon :01:00.0:   SRBM_STATUS   = 0x20C0
  [  157.521703] radeon :01:00.0:   SRBM_STATUS2  = 0x
  [  157.521708] radeon :01:00.0:   R_008674_CP_STALLED_STAT1 = 0x
  [  157.521714] radeon :01:00.0:   R_008678_CP_STALLED_STAT2 = 0x
  [  157.521719] radeon :01:00.0:   R_00867C_CP_BUSY_STAT = 0x
  [  157.521724] radeon :01:00.0:   R_008680_CP_STAT  = 0x
  [  157.521730] radeon :01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
  [  157.521750] radeon :01:00.0: GPU reset succeeded, trying to resume
  [  157.544993] [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
  [  157.547598] [drm] PCIE GART of 1024M enabled (table at 0x00274000).
  [  157.547689] radeon :01:00.0: WB enabled
  [  157.547692] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x8800cf551c00
  [  157.547694] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x8800cf551c0c
  [  157.549250] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00072118 and cpu addr 0xc90002032118
  [  157.771955] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test 
failed (scratch(0x8504)=0xCAFEDEAD)
  [  157.771978] [drm:evergreen_resume [radeon]] *ERROR* evergreen startup 
failed on resume

  
  Software version information:

  % cat /proc/version
  Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 
(Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016

  % dpkg -l firefox vlc
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: 

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

[iBART]

mich@ezbook:~$ uname -a
Linux ezbook 4.14.0-997-generic #201712022100 SMP Sun Dec 3 02:02:11 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

mich@ezbook:~$ dmesg | grep JUMPER
[0.00] DMI: Jumper EZbook/P313R, BIOS JUMPER2x.P8.WP313R.NHNAUHN05 
09/30/2017


mich@ezbook:~$ xinput --list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ MI Dongle MI Wireless Mouse   id=9[slave  pointer  (2)]
⎜   ↳ MI Dongle MI Wireless Mouse   id=10   [slave  pointer  (2)]
⎜   ↳ SYNA3602:00 0911:5288 Touchpadid=12   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Video Bus id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ MI Dongle MI Wireless Mouse   id=8[slave  keyboard (3)]
↳ USB 2.0 Camera: USB 2.0 Cameraid=11   [slave  keyboard (3)]
↳ Intel HID 5 button array  id=13   [slave  keyboard (3)]
↳ Intel HID events  id=14   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=15   [slave  keyboard (3)]
↳ MI Dongle MI Wireless Mouse   id=16   [slave  keyboard (3)]
↳ MI Dongle MI Wireless Mouse   id=17   [slave  keyboard (3)]

mich@ezbook:~$ xinput list 12
SYNA3602:00 0911:5288 Touchpad  id=12   [slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 12. Type: XIButtonClass
Buttons supported: 12
Button labels: "Button Left" "Button Middle" "Button Right" 
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz 
Wheel Right" None None None None None
Button state:
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 0:
  Label: Rel X
  Range: 0.00 - 1310.00
  Resolution: 14000 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 1:
  Label: Rel Y
  Range: 0.00 - 859.00
  Resolution: 14000 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 2:
  Label: Rel Horiz Scroll
  Range: 0.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIValuatorClass
Detail for Valuator 3:
  Label: Rel Vert Scroll
  Range: 0.00 - -1.00
  Resolution: 0 units/m
  Mode: relative
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 31.00
  flags: 0x0
Class originated from: 12. Type: XIScrollClass
Scroll info for Valuator 3
  type: 1 (vertical)
  increment: 31.00
  flags: 0x0

mich@ezbook:~$ xinput list-props "SYNA3602:00 0911:5288 Touchpad"
Device 'SYNA3602:00 0911:5288 Touchpad':
Device Enabled (141):   1
Coordinate Transformation Matrix (143): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (271): 1
Device Accel Constant Deceleration (272):   2.50
Device Accel Adaptive Deceleration (273):   1.00
Device Accel Velocity Scaling (274):12.50
Synaptics Edges (293):  52, 1258, 46, 813
Synaptics Finger (294): 25, 30, 0
Synaptics Tap Time (295):   180
Synaptics Tap Move (296):   68
Synaptics Tap Durations (297):  180, 180, 100
Synaptics ClickPad (298):   1
Synaptics Middle Button Timeout (299):  0
Synaptics Two-Finger Pressure (300):282
Synaptics Two-Finger Width (301):   7
Synaptics Scrolling Distance (302): 31, 31
Synaptics Edge Scrolling (303): 0, 0, 0
Synaptics Two-Finger Scrolling (304):   1, 1
Synaptics Move Speed (305): 1.00, 1.75, 0.127714, 0.00
Synaptics Off (306):2
Synaptics Locked Drags (307):   0
Synaptics Locked Drags Timeout (308):   5000
Synaptics Tap Action (309): 2, 3, 0, 0, 1, 3, 0
Synaptics Click Action (310):   1, 1, 0
Synaptics Circular Scrolling (311): 0
Synaptics Circular Scrolling Distance (312):0.10

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Antonio Ribezzi]

I have a Lenovo G50-70, and my laptop was affected when I upgraded to
Ubuntu 17.10. #284 saved my laptop, I installed Linux kernel 4.18.8,
rebooted and my bios was working properly again. Thank you so much
drhamster!

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

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

[Matt G]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1740175/+attachment/5027698/+files/ProcCpuinfoMinimal.txt

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

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

Title:
  Ubuntu 17.10 not resuming from suspend, freezing on shut down

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on an Acer Espire with intel microcode running dual boot Xorg
  17.10 using Gnome. I'd say it's usually 50/50 that i'm able to suspend
  and successfully resume. Same goes for shutting down now, where it
  will freeze on the purple Ubuntu screen. When I suspend, the monitor
  will go out but the hard drive will still be running and I have to
  hard power off. Here's a pm-suspend log:

  Initial commandline parameters: 
  Fri Dec 22 16:24:14 EST 2017: Running hooks for suspend.
  Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
  /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/000record-status suspend suspend:
  /usr/lib/pm-utils/sleep.d/000record-status suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
  Linux qs-ubuntu 4.14.8-041408-generic #201712200555 SMP Wed Dec 20 10:57:38 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  Module  Size  Used by
  msr16384  0
  ccm20480  6
  binfmt_misc20480  1
  nls_iso8859_1  16384  1
  ath3k  20480  0
  uvcvideo   86016  0
  videobuf2_vmalloc  16384  1 uvcvideo
  videobuf2_memops   16384  1 videobuf2_vmalloc
  videobuf2_v4l2 24576  1 uvcvideo
  btusb  45056  0
  btrtl  16384  1 btusb
  videobuf2_core 40960  2 uvcvideo,videobuf2_v4l2
  btbcm  16384  1 btusb
  videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
  media  40960  2 uvcvideo,videodev
  cmdlinepart16384  0
  btintel16384  1 btusb
  bluetooth 540672  6 btrtl,btintel,btbcm,ath3k,btusb
  ecdh_generic   24576  1 bluetooth
  intel_spi_platform 16384  0
  intel_spi  20480  1 intel_spi_platform
  spi_nor32768  1 intel_spi
  joydev 20480  0
  mtd57344  4 spi_nor,intel_spi,cmdlinepart
  intel_rapl 20480  0
  x86_pkg_temp_thermal16384  0

  I attached the dmesg.log.

  I'm pretty new to linux, so please let me know if there's another log I 
should get for more details. I upgraded to kernel 4.14.8-041408-generic last 
week, which didn't help.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-16 (101 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful
  Uname: Linux 4.14.8-041408-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to artful on 2017-10-20 (66 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1740175] Re: Ubuntu 17.10 not resuming from suspend, freezing on shut down

[Matt G]

apport information

** Tags added: apport-collected

** Description changed:

  I'm on an Acer Espire with intel microcode running dual boot Xorg 17.10
  using Gnome. I'd say it's usually 50/50 that i'm able to suspend and
  successfully resume. Same goes for shutting down now, where it will
  freeze on the purple Ubuntu screen. When I suspend, the monitor will go
  out but the hard drive will still be running and I have to hard power
  off. Here's a pm-suspend log:
  
  Initial commandline parameters: 
  Fri Dec 22 16:24:14 EST 2017: Running hooks for suspend.
  Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
  /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.
  
  Running hook /usr/lib/pm-utils/sleep.d/000record-status suspend suspend:
  /usr/lib/pm-utils/sleep.d/000record-status suspend suspend: success.
  
  Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
  Linux qs-ubuntu 4.14.8-041408-generic #201712200555 SMP Wed Dec 20 10:57:38 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  Module  Size  Used by
  msr16384  0
  ccm20480  6
  binfmt_misc20480  1
  nls_iso8859_1  16384  1
  ath3k  20480  0
  uvcvideo   86016  0
  videobuf2_vmalloc  16384  1 uvcvideo
  videobuf2_memops   16384  1 videobuf2_vmalloc
  videobuf2_v4l2 24576  1 uvcvideo
  btusb  45056  0
  btrtl  16384  1 btusb
  videobuf2_core 40960  2 uvcvideo,videobuf2_v4l2
  btbcm  16384  1 btusb
  videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
  media  40960  2 uvcvideo,videodev
  cmdlinepart16384  0
  btintel16384  1 btusb
  bluetooth 540672  6 btrtl,btintel,btbcm,ath3k,btusb
  ecdh_generic   24576  1 bluetooth
  intel_spi_platform 16384  0
  intel_spi  20480  1 intel_spi_platform
  spi_nor32768  1 intel_spi
  joydev 20480  0
  mtd57344  4 spi_nor,intel_spi,cmdlinepart
  intel_rapl 20480  0
  x86_pkg_temp_thermal16384  0
  
  I attached the dmesg.log.
  
- I'm pretty new to linux, so please let me know if there's another log I
- should get for more details. I upgraded to kernel 4.14.8-041408-generic
- last week, which didn't help.
+ I'm pretty new to linux, so please let me know if there's another log I 
should get for more details. I upgraded to kernel 4.14.8-041408-generic last 
week, which didn't help.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.6
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2017-09-16 (101 days ago)
+ InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags:  artful
+ Uname: Linux 4.14.8-041408-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to artful on 2017-10-20 (66 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1740175/+attachment/5027697/+files/JournalErrors.txt

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

Title:
  Ubuntu 17.10 not resuming from suspend, freezing on shut down

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on an Acer Espire with intel microcode running dual boot Xorg
  17.10 using Gnome. I'd say it's usually 50/50 that i'm able to suspend
  and successfully resume. Same goes for shutting down now, where it
  will freeze on the purple Ubuntu screen. When I suspend, the monitor
  will go out but the hard drive will still be running and I have to
  hard power off. Here's a pm-suspend log:

  Initial commandline parameters: 
  Fri Dec 22 16:24:14 EST 2017: Running hooks for suspend.
  Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
  /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/000record-status suspend suspend:
  /usr/lib/pm-utils/sleep.d/000record-status suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
  Linux qs-ubuntu 4.14.8-041408-generic #201712200555 SMP Wed Dec 20 10:57:38 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  Module  Size  Used by
  msr16384  0
  ccm20480  6
  binfmt_misc20480  1
  nls_iso8859_1  16384  1
  ath3k  20480  0
  uvcvideo   86016  0
  videobuf2_vmalloc  16384  1 uvcvideo
  videobuf2_memops   

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

[Ubuntu Kernel Bot]

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

apport-collect 1740175

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

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

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

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

** Tags added: artful

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

Title:
  Ubuntu 17.10 not resuming from suspend, freezing on shut down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on an Acer Espire with intel microcode running dual boot Xorg
  17.10 using Gnome. I'd say it's usually 50/50 that i'm able to suspend
  and successfully resume. Same goes for shutting down now, where it
  will freeze on the purple Ubuntu screen. When I suspend, the monitor
  will go out but the hard drive will still be running and I have to
  hard power off. Here's a pm-suspend log:

  Initial commandline parameters: 
  Fri Dec 22 16:24:14 EST 2017: Running hooks for suspend.
  Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
  /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/000record-status suspend suspend:
  /usr/lib/pm-utils/sleep.d/000record-status suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
  Linux qs-ubuntu 4.14.8-041408-generic #201712200555 SMP Wed Dec 20 10:57:38 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  Module  Size  Used by
  msr16384  0
  ccm20480  6
  binfmt_misc20480  1
  nls_iso8859_1  16384  1
  ath3k  20480  0
  uvcvideo   86016  0
  videobuf2_vmalloc  16384  1 uvcvideo
  videobuf2_memops   16384  1 videobuf2_vmalloc
  videobuf2_v4l2 24576  1 uvcvideo
  btusb  45056  0
  btrtl  16384  1 btusb
  videobuf2_core 40960  2 uvcvideo,videobuf2_v4l2
  btbcm  16384  1 btusb
  videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
  media  40960  2 uvcvideo,videodev
  cmdlinepart16384  0
  btintel16384  1 btusb
  bluetooth 540672  6 btrtl,btintel,btbcm,ath3k,btusb
  ecdh_generic   24576  1 bluetooth
  intel_spi_platform 16384  0
  intel_spi  20480  1 intel_spi_platform
  spi_nor32768  1 intel_spi
  joydev 20480  0
  mtd57344  4 spi_nor,intel_spi,cmdlinepart
  intel_rapl 20480  0
  x86_pkg_temp_thermal16384  0

  I attached the dmesg.log.

  I'm pretty new to linux, so please let me know if there's another log I 
should get for more details. I upgraded to kernel 4.14.8-041408-generic last 
week, which didn't help.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-16 (101 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful
  Uname: Linux 4.14.8-041408-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to artful on 2017-10-20 (66 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

Re: [Kernel-packages] [Bug 1737316] Re: Having installed 17.10 I'm getting hardware errors on boot

[James Spreadbury]

Hi there.

Having played with this a bit more, each time you update the kernel it
seems to boot ok, but the only rarely.  Does that tell us anything.

The first error after the i915 errors begins failed to start volatile
files...

Subsequent errors include 'Failed to start install and generate colour
profiles.

Does that tell you anything?

16.04LTS is still rock solid.


On 14 December 2017 14:17:26 GMT+00:00, Joseph Salisbury 
 wrote:
>Can you give the latest 4.13 upstream stable kernel a try:
>http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.16/
>
>-- 
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1737316
>
>Title:
>  Having installed 17.10 I'm getting hardware errors on boot
>
>Status in linux package in Ubuntu:
>  Incomplete
>
>Bug description:
>  I'm getting the i915 uncleared fifo underrun on pipe A errors.
>
>  The system won't boot cleanly.  I'm using Xorg rather than Wayland as
>  that appears to be a bit more stable.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
>  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
>  Uname: Linux 4.13.0-17-generic x86_64
>  ApportVersion: 2.20.7-0ubuntu3.5
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC1:  james  3855 F pulseaudio
>   /dev/snd/controlC0:  james  3855 F pulseaudio
>  CurrentDesktop: ubuntu:GNOME
>  Date: Sat Dec  9 12:31:31 2017
>  HibernationDevice: RESUME=UUID=d7a968e5-99de-41f8-b764-381e913ec11d
>  InstallationDate: Installed on 2014-09-12 (1184 days ago)
>InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
>(20140722.2)
>  Lsusb:
>   Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. 
>   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  MachineType: Hewlett-Packard HP 15 Notebook PC
>  ProcFB: 0 inteldrmfb
>ProcKernelCmdLine:
>BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed
>root=UUID=c8fe4fc7-a4b3-4389-a0f7-06593d9cf223 ro quiet splash
>  RelatedPackageVersions:
>   linux-restricted-modules-4.13.0-17-generic N/A
>   linux-backports-modules-4.13.0-17-generic  N/A
>   linux-firmware 1.169
>  RfKill:
>   0: phy0: Wireless LAN
>   Soft blocked: no
>   Hard blocked: no
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to artful on 2017-12-02 (6 days ago)
>  dmi.bios.date: 05/21/2014
>  dmi.bios.vendor: Insyde
>  dmi.bios.version: F.18
>  dmi.board.asset.tag: Type2 - Board Asset Tag
>  dmi.board.name: 2211
>  dmi.board.vendor: Hewlett-Packard
>  dmi.board.version: 86.28
>  dmi.chassis.asset.tag: Chassis Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Hewlett-Packard
>  dmi.chassis.version: Chassis Version
>dmi.modalias:
>dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2211:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
>  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
>  dmi.product.name: HP 15 Notebook PC
>  dmi.product.version: 097610405F0620180
>  dmi.sys.vendor: Hewlett-Packard
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737316/+subscriptions

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Title:
  Having installed 17.10 I'm getting hardware errors on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm getting the i915 uncleared fifo underrun on pipe A errors.

  The system won't boot cleanly.  I'm using Xorg rather than Wayland as
  that appears to be a bit more stable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  3855 F pulseaudio
   /dev/snd/controlC0:  james  3855 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  9 12:31:31 2017
  HibernationDevice: RESUME=UUID=d7a968e5-99de-41f8-b764-381e913ec11d
  InstallationDate: Installed on 2014-09-12 (1184 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 

[Kernel-packages] [Bug 1740175] [NEW] Ubuntu 17.10 not resuming from suspend, freezing on shut down

[Matt G]

Public bug reported:

I'm on an Acer Espire with intel microcode running dual boot Xorg 17.10
using Gnome. I'd say it's usually 50/50 that i'm able to suspend and
successfully resume. Same goes for shutting down now, where it will
freeze on the purple Ubuntu screen. When I suspend, the monitor will go
out but the hard drive will still be running and I have to hard power
off. Here's a pm-suspend log:

Initial commandline parameters: 
Fri Dec 22 16:24:14 EST 2017: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
/usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/000record-status suspend suspend:
/usr/lib/pm-utils/sleep.d/000record-status suspend suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux qs-ubuntu 4.14.8-041408-generic #201712200555 SMP Wed Dec 20 10:57:38 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
Module  Size  Used by
msr16384  0
ccm20480  6
binfmt_misc20480  1
nls_iso8859_1  16384  1
ath3k  20480  0
uvcvideo   86016  0
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_v4l2 24576  1 uvcvideo
btusb  45056  0
btrtl  16384  1 btusb
videobuf2_core 40960  2 uvcvideo,videobuf2_v4l2
btbcm  16384  1 btusb
videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
media  40960  2 uvcvideo,videodev
cmdlinepart16384  0
btintel16384  1 btusb
bluetooth 540672  6 btrtl,btintel,btbcm,ath3k,btusb
ecdh_generic   24576  1 bluetooth
intel_spi_platform 16384  0
intel_spi  20480  1 intel_spi_platform
spi_nor32768  1 intel_spi
joydev 20480  0
mtd57344  4 spi_nor,intel_spi,cmdlinepart
intel_rapl 20480  0
x86_pkg_temp_thermal16384  0

I attached the dmesg.log.

I'm pretty new to linux, so please let me know if there's another log I
should get for more details. I upgraded to kernel 4.14.8-041408-generic
last week, which didn't help.

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

** Attachment added: "dmesg.log"
   https://bugs.launchpad.net/bugs/1740175/+attachment/5027688/+files/dmesg.log

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

Title:
  Ubuntu 17.10 not resuming from suspend, freezing on shut down

Status in linux package in Ubuntu:
  New

Bug description:
  I'm on an Acer Espire with intel microcode running dual boot Xorg
  17.10 using Gnome. I'd say it's usually 50/50 that i'm able to suspend
  and successfully resume. Same goes for shutting down now, where it
  will freeze on the purple Ubuntu screen. When I suspend, the monitor
  will go out but the hard drive will still be running and I have to
  hard power off. Here's a pm-suspend log:

  Initial commandline parameters: 
  Fri Dec 22 16:24:14 EST 2017: Running hooks for suspend.
  Running hook /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend:
  /usr/lib/pm-utils/sleep.d/000kernel-change suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/000record-status suspend suspend:
  /usr/lib/pm-utils/sleep.d/000record-status suspend suspend: success.

  Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
  Linux qs-ubuntu 4.14.8-041408-generic #201712200555 SMP Wed Dec 20 10:57:38 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  Module  Size  Used by
  msr16384  0
  ccm20480  6
  binfmt_misc20480  1
  nls_iso8859_1  16384  1
  ath3k  20480  0
  uvcvideo   86016  0
  videobuf2_vmalloc  16384  1 uvcvideo
  videobuf2_memops   16384  1 videobuf2_vmalloc
  videobuf2_v4l2 24576  1 uvcvideo
  btusb  45056  0
  btrtl  16384  1 btusb
  videobuf2_core 40960  2 uvcvideo,videobuf2_v4l2
  btbcm  16384  1 btusb
  videodev  176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
  media  40960  2 uvcvideo,videodev
  cmdlinepart16384  0
  btintel16384  1 btusb
  bluetooth 540672  6 btrtl,btintel,btbcm,ath3k,btusb
  ecdh_generic   24576  1 bluetooth
  intel_spi_platform 16384  0
  intel_spi  20480  1 intel_spi_platform
  spi_nor32768  1 intel_spi
  joydev 20480  0
  mtd57344  4 spi_nor,intel_spi,cmdlinepart
  intel_rapl 20480  0
  x86_pkg_temp_thermal16384  0

  I attached the dmesg.log.

  I'm pretty new to linux, so please let me know if there's another log
  I 

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Bug]

Hi,
I just bought Lenovo Yoga 720-15IKB with InsydeH20 bios V1.10 and I need Linux 
for my work.
Nobody (yet) reported bricked issues on this version of laptop, I saw that 
latest Fedora version comes with Kernel 4.14 and now Im in doubt is it safe to 
install latest Fedora with kernel 4.14 or to wait more?

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1727320] Re: Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470]

[Luca]

This bug is not a duplicate of bug #1505409, unfortunately I don't have
the laptop anymore and I cannot say it's kernel related, but it may be a
combination of kernel/graphics stack that shows an additional display
due to the Displayport 1.2 capability.

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

Title:
  Screen turn on/off 3 times and DP-1-3 connected but nothing is
  connected [latitude e7470]

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

Bug description:
  Gnome-shell crash and restart after the login and the screen flicker 1
  time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470
  laptop.

  If I go in display settings I notice a second monitor Synaptics Inc
  24'' which doesn't exist in reality. In Wayland after the screen stop
  flickering I don't have any other problem and that monitor is not
  present there.

  xrandr | grep -i ' connected'
  eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
  DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have 
anything connected to this port

  With Fedora 26 I don't have this problem but I'm not yet able to find what 
package is the culprit.
  I believe this problem is related to Displayport 1.2, I don't have any dock 
nor I need to connect more than 1 monitor and would be satisfied just having 
one interface.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Oct 25 11:46:16 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1727320

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

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

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

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

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

Title:
  Screen turn on/off 3 times and DP-1-3 connected but nothing is
  connected [latitude e7470]

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

Bug description:
  Gnome-shell crash and restart after the login and the screen flicker 1
  time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470
  laptop.

  If I go in display settings I notice a second monitor Synaptics Inc
  24'' which doesn't exist in reality. In Wayland after the screen stop
  flickering I don't have any other problem and that monitor is not
  present there.

  xrandr | grep -i ' connected'
  eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
  DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have 
anything connected to this port

  With Fedora 26 I don't have this problem but I'm not yet able to find what 
package is the culprit.
  I believe this problem is related to Displayport 1.2, I don't have any dock 
nor I need to connect more than 1 monitor and would be satisfied just having 
one interface.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Oct 25 11:46:16 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Dan Bright]

I have the same issue on my Lenovo Z50-70. Only just noticed, as have
been running 17.10 since late beta and haven't needed to touch UEFI.

I've been running all manner of Linux distros on my systems for a decade
and this is the first time anything has actually corrupted the hardware
firmware (BIOS/UEFI).

More fool me for installing a non LTS I suppose. I simply cannot afford
to replace this machine at the moment, and from current reports it
appears that come the next time I need to reinstall for any reason my
laptop is, to all intents and purposes, bricked. Not amused. At all.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1727320] Re: Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470]

[Luca]

** This bug is no longer a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

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

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

Title:
  Screen turn on/off 3 times and DP-1-3 connected but nothing is
  connected [latitude e7470]

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Gnome-shell crash and restart after the login and the screen flicker 1
  time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470
  laptop.

  If I go in display settings I notice a second monitor Synaptics Inc
  24'' which doesn't exist in reality. In Wayland after the screen stop
  flickering I don't have any other problem and that monitor is not
  present there.

  xrandr | grep -i ' connected'
  eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
  DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have 
anything connected to this port

  With Fedora 26 I don't have this problem but I'm not yet able to find what 
package is the culprit.
  I believe this problem is related to Displayport 1.2, I don't have any dock 
nor I need to connect more than 1 monitor and would be satisfied just having 
one interface.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Oct 25 11:46:16 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Kernel-packages] [Bug 1627474] Re: ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)

[Kostadin Stoilov]

This bug is still present in Ubuntu 17.10 Artful. I have experienced it
after waking up from suspend on a Dell XPS 9360 with a clean Ubuntu
install.

Here is the dump:

Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.661562] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.694143] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.726760] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.759262] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.791956] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.824470] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.857075] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.889653] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.922200] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30476.954870] ath10k_pci :3a:00.0: 
failed to wake target for read32 at 0x0003a028: -110
Dec 26 17:52:04 sabina-XPS-13 kernel: [30477.569491] ath10k_pci :3a:00.0: 
failed to read device register, device is gone
Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669015] ath10k_pci :3a:00.0: 
firmware crashed! (uuid 283c1469-65cc-447c-a08d-c723b4f1387a)
Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669020] ath10k_pci :3a:00.0: 
qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535
Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669021] ath10k_pci :3a:00.0: 
kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669389] ath10k_pci :3a:00.0: 
firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp 
crc32 4d458559
Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669634] ath10k_pci :3a:00.0: 
board_file api 2 bmi_id N/A crc32 07ee144e
Dec 26 17:52:05 sabina-XPS-13 kernel: [30477.669635] ath10k_pci :3a:00.0: 
htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.172084] ath10k_pci :3a:00.0: 
failed to read firmware dump area: -16
Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.172087] ath10k_pci :3a:00.0: 
Copy Engine register dump:
Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.302279] ath10k_pci :3a:00.0: 
[00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.434224] ath10k_pci :3a:00.0: 
[01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:05 sabina-XPS-13 kernel: [30478.565730] ath10k_pci :3a:00.0: 
[02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:06 sabina-XPS-13 kernel: [30478.695977] ath10k_pci :3a:00.0: 
[03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:06 sabina-XPS-13 kernel: [30478.826324] ath10k_pci :3a:00.0: 
[04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:06 sabina-XPS-13 kernel: [30478.956700] ath10k_pci :3a:00.0: 
[05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.086854] ath10k_pci :3a:00.0: 
[06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.217234] ath10k_pci :3a:00.0: 
[07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.217242] ath10k_pci :3a:00.0: 
failed to reset chip: -5
Dec 26 17:52:06 sabina-XPS-13 kernel: [30479.217244] ath10k_pci :3a:00.0: 
Could not init hif: -5

The workaround is to manually update to the linux-firmware package in
bionic (1.170)

Dell have written an article about it:

http://www.dell.com/support/article/bg/en/bgbsdt1/sln306440/killer-n1535
-wireless-firmware-manual-update-guide-for-ubuntu-systems?lang=en

I have been running the package and so far so good.

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

Title:
  ath10k_pci :03:00.0: firmware crashed! (uuid n/a)

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

Bug description:
  The wireless card in my Acer V3-372-587T suffers from firmware crashes
  regularly (every 5-10mins approx).

  $ lsb_release -rd
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10

  Checking dmesg I see:

  $ dmesg | grep ath10k 
  [91/214]
  [   

[Kernel-packages] [Bug 1740143] Re: backport btrfs ssd mount option fix

[Vasya Pupkin]

This backport request does not miss anything. Also, the apport-collect
1740143 doesn't seem to do anything after opening this bug page in
ELinks.

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

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

Title:
  backport btrfs ssd mount option fix

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  It appears that all kernels before 4.14 had a problem with btrfs ssd
  mount option. According to
  https://btrfs.wiki.kernel.org/index.php/Gotchas#ssd_mount_option, it
  has a negative impact on usability and lifetime of modern SSDs. Since
  it is enabled by default when SSD is detected, it affects all systems
  with SSD drives. Please backport this commit to normal and HWE
  kernels:
  
https://github.com/torvalds/linux/commit/583b723151794e2ff1691f1510b4e43710293875

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.104.109
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 дек 17 10:50 seq
   crw-rw 1 root audio 116, 33 дек 17 10:50 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-104-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Dec 26 18:57:10 2017
  InstallationDate: Installed on 2011-04-14 (2448 days ago)
  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PciMultimedia:
   
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=c7605446-0bf3-11e7-bfa0-f91abd974ce1 ro quiet bootdegraded=true
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (513 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/20/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: 4Core1333-eSATA2.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/20/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn4Core1333-eSATA2.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1740143

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

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

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

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

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

Title:
  backport btrfs ssd mount option fix

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  It appears that all kernels before 4.14 had a problem with btrfs ssd
  mount option. According to
  https://btrfs.wiki.kernel.org/index.php/Gotchas#ssd_mount_option, it
  has a negative impact on usability and lifetime of modern SSDs. Since
  it is enabled by default when SSD is detected, it affects all systems
  with SSD drives. Please backport this commit to normal and HWE
  kernels:
  
https://github.com/torvalds/linux/commit/583b723151794e2ff1691f1510b4e43710293875

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.104.109
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 дек 17 10:50 seq
   crw-rw 1 root audio 116, 33 дек 17 10:50 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-104-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Dec 26 18:57:10 2017
  InstallationDate: Installed on 2011-04-14 (2448 days ago)
  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PciMultimedia:
   
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=c7605446-0bf3-11e7-bfa0-f91abd974ce1 ro quiet bootdegraded=true
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (513 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/20/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: 4Core1333-eSATA2.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/20/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn4Core1333-eSATA2.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[ed withnell]

I also Have this bug on an Acer Aspire ES1-512 InsydeH20 bios V1.09 it sees the 
usb but wont save changes to bios no dvd rom installed in this model 
this laptop boots fine into Ubuntu 17.10 (Removed Windows 10 during install).it 
has some other minor problems. trackpad not working. (not used)
it does also hang during reboot or shutdown requiring use of hardware button

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Thomas P.]

Retried with recent instructions from mrgromov in post 
https://github.com/kuba-moo/mt7601u/issues/64 and got it to work. 
Would it be possible to create a fix or is this particular device buggy?

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  

[Kernel-packages] [Bug 1740143] [NEW] backport btrfs ssd mount option fix

[Vasya Pupkin]

Public bug reported:

Hello,

It appears that all kernels before 4.14 had a problem with btrfs ssd
mount option. According to
https://btrfs.wiki.kernel.org/index.php/Gotchas#ssd_mount_option, it has
a negative impact on usability and lifetime of modern SSDs. Since it is
enabled by default when SSD is detected, it affects all systems with SSD
drives. Please backport this commit to normal and HWE kernels:
https://github.com/torvalds/linux/commit/583b723151794e2ff1691f1510b4e43710293875

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.104.109
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 дек 17 10:50 seq
 crw-rw 1 root audio 116, 33 дек 17 10:50 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-104-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Tue Dec 26 18:57:10 2017
InstallationDate: Installed on 2011-04-14 (2448 days ago)
InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PciMultimedia:
 
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=c7605446-0bf3-11e7-bfa0-f91abd974ce1 ro quiet bootdegraded=true
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-104-generic N/A
 linux-backports-modules-4.4.0-104-generic  N/A
 linux-firmware 1.157.14
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-07-30 (513 days ago)
WifiSyslog:
 
dmi.bios.date: 02/20/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: 4Core1333-eSATA2.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/20/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn4Core1333-eSATA2.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug xenial

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

Title:
  backport btrfs ssd mount option fix

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  It appears that all kernels before 4.14 had a problem with btrfs ssd
  mount option. According to
  https://btrfs.wiki.kernel.org/index.php/Gotchas#ssd_mount_option, it
  has a negative impact on usability and lifetime of modern SSDs. Since
  it is enabled by default when SSD is detected, it affects all systems
  with SSD drives. Please backport this commit to normal and HWE
  kernels:
  
https://github.com/torvalds/linux/commit/583b723151794e2ff1691f1510b4e43710293875

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.104.109
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 дек 17 10:50 seq
   crw-rw 1 root audio 116, 33 дек 17 10:50 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-104-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Dec 26 18:57:10 2017
  InstallationDate: Installed on 2011-04-14 (2448 days ago)
  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 
(20110211.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PciMultimedia:
   
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=c7605446-0bf3-11e7-bfa0-f91abd974ce1 ro quiet bootdegraded=true
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: 

[Kernel-packages] [Bug 1651435] Re: BTRFS error: could not find root 8

[jth]

Hi
According to this it is nothing to worry about.

systemd is probing and if quota disabled as it is by default, this will
show.

https://www.mail-archive.com/search?l=linux-
bt...@vger.kernel.org=subject:%22Re%5C%3A+BTRFS%5C%3A+could+not+find+root+8%22=newest=1

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

Title:
  BTRFS error: could not find root 8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a KVM guest system which was running for some time now (142
  days uptime).

  Today, I logged in for the first time since months, and got an error
  message in syslog (and console):

  kernel: BTRFS error (device vda2): could not find root 8

  The error happened together with my login (in respect to the date of
  the log entry).

  The system was running with kernel 4.4.0-31-generic when the problem
  occured.

  When googling around, I found some similar results, but nowhere is
  mentioned that this got fixed somehow.

  So far, I could not find anything harmful (I did not reboot yet,
  however).

  I updated the kernel now, eventually that helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Dec 20 13:00 seq
   crw-rw+ 1 root audio 116, 33 Dec 20 13:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Dec 20 13:40:44 2016
  HibernationDevice: RESUME=UUID=419693f3-cd92-4870-a16a-7bede16d9b8a
  InstallationDate: Installed on 2016-06-20 (182 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=ebfbbec2-f4df-4e40-92a5-3db6b57eb8f5 ro rootflags=subvol=@
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20140531_083030-gandalf
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20140531_083030-gandalf:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.1:cvnQEMU:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: QEMU
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-57-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2013-08-21 (1229 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IwConfig:
   em1   no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic 
root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@ 
pcie_aspm=force "acpi_osi=!Windows 2012" 

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[Ruben]

I have the same or a similar problem on kernel version 4.13.4, Ubuntu
17.10.

Not sure whether it is exactly the same though. In syslog I see the FIFO
underrun message is preceded by a lot of other ERROR messages:

Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.055663] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.055726] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.072359] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.072425] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.089055] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.089122] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.105722] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.105788] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.112465] 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.139057] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080
Dec 26 14:33:59 ruben-Precision-5520 kernel: [ 4152.139116] 
[drm:gen8_irq_handler [i915]] *ERROR* Fault errors on pipe A: 0x0080

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 

Re: [Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[Mario Limonciello]

Yeah it does go to sleep after no use with those settings activated. It's
supposed to disappear from fwupd as a result too so I expected a different
error than that. But if you went really really fast I suppose that's a
possibility.

On Tue, Dec 26, 2017, 05:55 wdoekes <1715...@bugs.launchpad.net> wrote:

> BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter
> Configuration:
>
> [x] Enable Thunderbolt(tm) Technology Support
> [ ] Enable Thunderbolt(tm) Adapter Boot Support
> [ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules
>
> (x) Security level - User Authorization
>
> 
>
> I have/had no devices attached to the Thunderbolt/USB-C socket.
>
> But like I said, I ran the command quickly after reboot. Perhaps it
> enumerated right after boot but went away after a while of disuse?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1715146
>
> Title:
>   Not Suspending When Lid is Closed Causing Heat Issue
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions
>

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.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.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[DiagonalArg]

Happening on attempted bootup of a Thinkpad W520, using a USB stick
loaded with Ubuntu 17.10 installer.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Dec 31 

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[DiagonalArg]

*That's the Ubuntu Mate 17.10 installer.  I get a repeated Call trace
which ends with the line, "perf: interrupt took too long (8809 > 8338),
lowering t_max_sample_rate to 22500.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME 

[Kernel-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Andreas Hasenack]

I had a super nice and detailed reply written here, but of course I lost
it. Browsers are stupid things sometimes. So here are the comments that
survived.

TL;DR:
firejail is known to fail on s390 because there is no thunderbird package for a 
mainframe. I emailed ubuntu-devel@ and also pinged #ubuntu-devel on irc. 
Switching the test bed from a container to a VM for s390 a while back allowed 
this new test to run.

Others are green, with the exception of trusty:
a) armhf: fails copying the device /dev/null elsewhere with -a, which equates 
to creating a device outside of tmp, which is forbidden. Last time this worked 
was when the test bed was on lxc in 2016. On lxd it doesn't work. The other 
architectures are not using lxd. We should probably add a constraint so that 
the test only runs in vms. Should it be added to the current SRU package for 
trusty?

b) ppc: a grub error:
Generating grub configuration file ...
grub-probe: error: not a directory.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1

I pinged #ubuntu-devel about it, since I have no idea how to setup and
run a ppc vm, but got no response:

https://irclogs.ubuntu.com/2017/12/07/%23ubuntu-devel.html#t19:33

ahasenack   is there something going on with setting up ppc64el autopkg 
tests in excuses? I have 3 different packages failing there with the same error 
19:33
ahasenack   grub-probe: error: not a directory. 19:33
ahasenack   run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 1  19:33
ahasenack   in trusty   19:33
ahasenack   
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/a/autopkgtest/20171207_002904_c5112@/log.gz
 is one of them

Got no response. I don't even know if grub is used in ppc.


Regarding amd64 smoke test, I've been using the updated package on my machine 
(artful/amd64).

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Zesty:
  Fix Committed
Status in iproute2 source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most 

[Kernel-packages] [Bug 1740131] sosreport

[bugproxy]

Default Comment by Bridge

** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1740131/+attachment/5027454/+files/sosreport-ltcalpine-lp9.dumplog-20171005131416.tar.xz

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

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

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

Title:
  kdump emits huge logs while copying dump

Status in linux package in Ubuntu:
  New

Bug description:
  --Problem Description---
  kdump emits huge logs while copying dump. Full log of a single dump is 
attached in the bug.

  ---uname output---
  Linux ltcalpine-lp9 4.13.0-12-generic #13-Ubuntu SMP Fri Sep 22 20:52:52 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type/Model = Power 8 pVM/8408-E8E

  Additional Info-
  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.13.0-12-generic 
root=UUID=861097e8-43d3-4335-83d3-6db421e20564 ro 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump and install debug kernel
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot once
  5. make sure kdump is enabled
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo "c" > /proc/sysrq-triggeer

  Expected:
  To print copy of dump only once in console.

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

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

[Kernel-packages] [Bug 1740131] [NEW] kdump emits huge logs while copying dump

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

--Problem Description---
kdump emits huge logs while copying dump. Full log of a single dump is attached 
in the bug.

---uname output---
Linux ltcalpine-lp9 4.13.0-12-generic #13-Ubuntu SMP Fri Sep 22 20:52:52 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type/Model = Power 8 pVM/8408-E8E

Additional Info-
# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.13.0-12-generic 
root=UUID=861097e8-43d3-4335-83d3-6db421e20564 ro 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
 
---Steps to Reproduce---
1. installed linux-crashdump and install debug kernel
2. edited the kdump-tools.cfg crashkernel cmdline to above
3. update-grub
4. reboot once
5. make sure kdump is enabled
6. echo 1 > /proc/sys/kernel/sysrq
7. echo "c" > /proc/sysrq-triggeer

Expected:
To print copy of dump only once in console.

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


** Tags: architecture-ppc64le bugnameltc-159671 severity-medium 
targetmilestone-inin---
-- 
kdump emits huge logs while copying dump
https://bugs.launchpad.net/bugs/1740131
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 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue

[wdoekes]

BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter
Configuration:

[x] Enable Thunderbolt(tm) Technology Support
[ ] Enable Thunderbolt(tm) Adapter Boot Support
[ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules

(x) Security level - User Authorization



I have/had no devices attached to the Thunderbolt/USB-C socket.

But like I said, I ran the command quickly after reboot. Perhaps it
enumerated right after boot but went away after a while of disuse?

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

Title:
  Not Suspending When Lid is Closed Causing Heat Issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu Budgie 17.04 64-bit. I installed the operating
  system and then when booted, I apt-get update and apt-get upgrade. I
  went to the coffee shop and used the system for a while. When I came
  home I left my laptop Dell XPS 9360 in its leather case and inside my
  laptop bag. I left to do some errands and came back to a really hot
  laptop and case. The system had not gone to sleep when I closed the
  lid and the computer was very hot. I have attached a copy of the log
  files.

  I then:

  sudo vi /etc/systemd/logind.conf

  Changed: HandleLidSwitchDocked=suspend

  when I close the lid now it gives me a password to login when I open the lid, 
but I am not sure if it is sleeping properly. Please assist, as I do not want 
my laptop battery damaged by this heat again.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shawn  1786 F pulseaudio
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-04 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.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.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Romaric Thibault]

I can add as well that I tried the Insyde BIOS recovery method, and the
BIOS is not able to make it, the computer come in an endless loop :
start, read BIOS.fd file, shutdown, start, read, shutdown...

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Romaric Thibault]

Hello,
I don't know if it's necessary to say, but I confirm the issue as well on my 
Acer Aspire E3-111... Since I installed Ubuntu 17.10, I can't anymore change 
any BIOS setting, excepted hour and date, all other settings can't be saved 
through reboots.

** Description changed:

  SRU Justification
  
  Impact: Many users are reporting issues with bios corruption with 17.10.
  This seems to stem from enabling the intel-spi-* drivers in the kernel,
  which don't appear to be ready for use on end-user machines.
  
  Fix: Disable this driver.
  
  Test Case: Fix has been verified by our HWE team on affected hardware.
  
  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.
  
  ---
  
  Hi all,
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!
  
   UPDATE (22/12/2017) 
  
  LENOVO machines affected so far (please add your affected model to this
  list):
  
  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY
  
  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
+ Acer Aspire E3-111-C0UM
  
  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that they
  are aware of issue but are not providing details.
  
  ---
  
  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885
  
  ---
  
  result from apport-collect 1734147:
  
  ---
  
  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO
  
  ---

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted 

[Kernel-packages] [Bug 1736947] Re: Very long boot time with Chelsio T320 10GBASE-R RNIC adapter

[Corsaire]

could this be related ?

https://www.spinics.net/lists/linux-rdma/msg57490.html

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

Title:
  Very long boot time with Chelsio T320 10GBASE-R RNIC adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Chelsio T320 10GBASE-R RNIC in my machine apparently
  triggering a very long boot time.

  I initially thought about a USB problem as I wrote in ticket #1704614
  but new tests showed me otherwise.

  booting with this parameters yield some interesting things:
  GRUB_CMDLINE_LINUX_DEFAULT="--verbose nosplash debug"

  
  [4.772733] hid-generic 0003:046D:C22D.0009: input,hiddev0,hidraw8: USB 
HID v1.11 Device [Logitech G510 Gaming Keyboard] on 
usb-:00:1d.0-1.8.1.2.2/input1
  [4.877277] usb 2-1.8.1.3.4: New USB device found, idVendor=046d, 
idProduct=c069
  [4.877360] usb 2-1.8.1.3.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [4.877440] usb 2-1.8.1.3.4: Product: USB Laser Mouse
  [4.877504] usb 2-1.8.1.3.4: Manufacturer: Logitech
  [4.883052] input: Logitech USB Laser Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8.1/2-1.8.1.3/2-1.8.1.3.4/2-1.8.1.3.4:1.0/0003:046D:C069.000A/input/input12
  [4.883391] hid-generic 0003:046D:C069.000A: input,hidraw9: USB HID v1.10 
Mouse [Logitech USB Laser Mouse] on usb-:00:1d.0-1.8.1.3.4/input0
  [   62.501496] systemd-udevd[110]: seq 1103 
'/devices/pci:00/:00:01.1/:02:00.0/net/eth0' is taking a long time
  [   91.836493] systemd-udevd[131]: error changing net interface name 'eth0' 
to 'enp2s0': File exists
  [   91.836583] systemd-udevd[131]: could not rename interface '3' from 'eth0' 
to 'enp2s0': File exists
  [   91.908818] raid6: sse2x1   gen()  5176 MB/s
  [   91.976808] raid6: sse2x1   xor()  5202 MB/s
  [   92.044810] raid6: sse2x2   gen() 10397 MB/s
  [   92.112810] raid6: sse2x2   xor()  8718 MB/s
  [   92.180800] raid6: sse2x4   gen() 15554 MB/s
  [   92.248797] raid6: sse2x4   xor() 11584 MB/s
  [   92.248872] raid6: using algorithm sse2x4 gen() 15554 MB/s

  
  systemd-udevd seems to get stuck quite a long time here.

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

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

Re: [Kernel-packages] [Bug 1737316] Re: Having installed 17.10 I'm getting hardware errors on boot

[James Spreadbury]

Hi Josh.

It seems that a lot of the errors I'm getting are related to Mysql.
What file do I need to edit in the boot process to remove that problem
and then we can see how stable the rest of the system is.


On 14 December 2017 14:17:26 GMT+00:00, Joseph Salisbury 
 wrote:
>Can you give the latest 4.13 upstream stable kernel a try:
>http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.16/
>
>-- 
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1737316
>
>Title:
>  Having installed 17.10 I'm getting hardware errors on boot
>
>Status in linux package in Ubuntu:
>  Incomplete
>
>Bug description:
>  I'm getting the i915 uncleared fifo underrun on pipe A errors.
>
>  The system won't boot cleanly.  I'm using Xorg rather than Wayland as
>  that appears to be a bit more stable.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
>  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
>  Uname: Linux 4.13.0-17-generic x86_64
>  ApportVersion: 2.20.7-0ubuntu3.5
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC1:  james  3855 F pulseaudio
>   /dev/snd/controlC0:  james  3855 F pulseaudio
>  CurrentDesktop: ubuntu:GNOME
>  Date: Sat Dec  9 12:31:31 2017
>  HibernationDevice: RESUME=UUID=d7a968e5-99de-41f8-b764-381e913ec11d
>  InstallationDate: Installed on 2014-09-12 (1184 days ago)
>InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
>(20140722.2)
>  Lsusb:
>   Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. 
>   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  MachineType: Hewlett-Packard HP 15 Notebook PC
>  ProcFB: 0 inteldrmfb
>ProcKernelCmdLine:
>BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed
>root=UUID=c8fe4fc7-a4b3-4389-a0f7-06593d9cf223 ro quiet splash
>  RelatedPackageVersions:
>   linux-restricted-modules-4.13.0-17-generic N/A
>   linux-backports-modules-4.13.0-17-generic  N/A
>   linux-firmware 1.169
>  RfKill:
>   0: phy0: Wireless LAN
>   Soft blocked: no
>   Hard blocked: no
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to artful on 2017-12-02 (6 days ago)
>  dmi.bios.date: 05/21/2014
>  dmi.bios.vendor: Insyde
>  dmi.bios.version: F.18
>  dmi.board.asset.tag: Type2 - Board Asset Tag
>  dmi.board.name: 2211
>  dmi.board.vendor: Hewlett-Packard
>  dmi.board.version: 86.28
>  dmi.chassis.asset.tag: Chassis Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Hewlett-Packard
>  dmi.chassis.version: Chassis Version
>dmi.modalias:
>dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2211:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
>  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
>  dmi.product.name: HP 15 Notebook PC
>  dmi.product.version: 097610405F0620180
>  dmi.sys.vendor: Hewlett-Packard
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737316/+subscriptions

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Title:
  Having installed 17.10 I'm getting hardware errors on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm getting the i915 uncleared fifo underrun on pipe A errors.

  The system won't boot cleanly.  I'm using Xorg rather than Wayland as
  that appears to be a bit more stable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  3855 F pulseaudio
   /dev/snd/controlC0:  james  3855 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  9 12:31:31 2017
  HibernationDevice: RESUME=UUID=d7a968e5-99de-41f8-b764-381e913ec11d
  InstallationDate: Installed on 2014-09-12 (1184 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Sven Jacobsen]

Lenovo Yoga 300-11IBY affected after Ubuntu 17.10 installation. Horrible 
situation, no more installation possible. Now the system works, but if an 
update will break something, the whole machine will be unusable. 
Interesting enough: another machine, Lenovo ideapad 100-14IBY, running on Bodhi 
Linux 4, based on Ubuntu 16.04 LTS, is also affected.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Andrey]

Hi. 
I'm surprised that this issue it has just found. I've met it already in May on 
my Lenovo E31-70 with Xubuntu 16.04.03. (initially laptop was bought with 
FreeDOS). I thought the problem was with BIOS which I reflashed about 1 year 
ago.
Local Lenovo support diverted me - said they can do nothing.

But - I need to recheck it today - after installing new kernel 4.14.08 - looks 
like the problem is solved. At least I could off Security boot and it survived 
reboot.
Also I've mentioned laptop tried to boot from external usb disk connected.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (22/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software.  Insyde is responding to emails acknowledging that
  they are aware of issue but are not providing details.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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