date:20180204

We need to use GFP_DMA32 for vmalloc, please try this kernel,

people.canonical.com/~khfeng/lp1742316-dma32/

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/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: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Wed Jan 10 00:42:24 2018
  HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456
  InstallationDate: Installed on 2016-02-13 (696 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 
(20151021)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force 
video=LVDS-1:d vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago)
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: AD2700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742316/+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 1742892] Comment bridged from LTC Bugzilla

2018-02-04 Thread bugproxy

--- Comment From indira.pr...@in.ibm.com 2018-02-05 01:07 EDT---
Test machine is just stabilised with latest PNOR & BMC levels. Will try to 
experiment with early qemu 2.11 whenever system is free from other tasks.

Regards,
Indira

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

Title:
  [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start
  the guest with more than 1 thread on ubuntu1804 KVM host machine.

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

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2018-01-07 
13:18:32 ==
  Problem Description:
  ===
  Not able to start the ubutnu1804 guest with more than 1 thread on ubuntu1804 
KVM host machine

  Steps to re-create:
  ==
  > Installed Ubuntu1804 on boslcp3 host.

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.13.0-17-generic

  > Installed qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
  packages

  root@boslcp3:/home# virsh version
  Compiled against library: libvirt 3.6.0
  Using library: libvirt 3.6.0
  Using API: QEMU 3.6.0
  Running hypervisor: QEMU 2.10.1

  > root@boslcp3:~# ppc64_cpu --smt
  SMT is off

  > Defined the guest boslcp3g1 from host machine

  root@boslcp3:/home# virsh list --all
   IdName   State
  
   - boslcp3g1  shut off

  Please cherry pick

  commit 45c940ba490df28cb87b993981a5f63df6bbb8db
  Author: Paul Mackerras 
  Date:   Fri Nov 18 17:43:30 2016 +1100

  KVM: PPC: Book3S HV: Treat POWER9 CPU threads as independent subcores


  > Started the guest and it fails with the error

  root@boslcp3:~# virsh start --console boslcp3g1
  error: Failed to start domain boslcp3g1
  error: internal error: process exited while connecting to monitor: 
2018-01-05T02:54:37.762120Z qemu-system-ppc64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/3 (label charserial0)
  2018-01-05T02:54:37.829236Z qemu-system-ppc64: Cannot support more than 1 
threads on PPC with KVM

  > Unable to start the guest with more than 1 Thread from Ubuntu1804
  KVM host machine.

  XML:
  
  root@boslcp3:/home# virsh dumpxml boslcp3g1
  
boslcp3g1
95374879-0ed3-4562-a00f-e47d9aaf285c
10485760
6291456
6291456

  

  

32

  /machine


  hvm
  
  
  


  
  


  power9
  
  


  


destroy
restart
coredump-restart

  /usr/bin/qemu-system-ppc64 
  




  
  




  
  




  
  

  
  

  
  


  
  


  
  




  
  


  
  


  
  

  
  

  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742892/+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 1746340] Re: Samsung SSD corruption (fsck needed)

I forgot to mention that I reinstalled windows and everything is fine.
Even did a benchmark test on the SSD and I'm downloading lots of files
to test

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb

[Kernel-packages] [Bug 1747354] Re: Update bluez to version 5.48 in bionic

** Attachment added: "bluez_5.48-0ubuntu2.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049025/+files/bluez_5.48-0ubuntu2.dsc

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1746340] Re: Samsung SSD corruption (fsck needed)

On debian (4.9) I didn't notice the issue but I didn't use much.
HOWEVER, when I do apt-get upgrade on debian I do get the issue. It just
updated the kernel file, didn't run the new kernel (a boot would have to
happen).


On v4.15 I didn't change the nvme_core.default_ps_max_latency_us=0, I guess. I 
did before upgrading to v4.15, I guess. But I can try again.

This is all very strange

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10

[Kernel-packages] [Bug 1747354] Re: Update bluez to version 5.48 in bionic

** Patch removed: "bluez_5.48-0ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049020/+files/bluez_5.48-0ubuntu1.debdiff

** Attachment removed: "bluez_5.48-0ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049022/+files/bluez_5.48-0ubuntu1.debian.tar.xz

** Attachment removed: "bluez_5.48-0ubuntu1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049023/+files/bluez_5.48-0ubuntu1.dsc

** Attachment added: "bluez_5.48-0ubuntu2.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049024/+files/bluez_5.48-0ubuntu2.debian.tar.xz

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747321] Re: randomly freezes

2018-02-04 Thread Gérard Bigot

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

** This bug has been marked a duplicate of bug 1747293
   randomly freezes

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

Title:
  randomly freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems to randomly freeze (mouse and keyboard) then, need to re-login and 
relaunch programs (what I was working on). Since it is random, do not know the 
cause.
  This report is sent immediately after the freeze/crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sheldon   10520 F pulseaudio
   /dev/snd/controlC1:  sheldon   10520 F pulseaudio
   /dev/snd/controlC0:  sheldon   10520 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 19:40:40 2018
  HibernationDevice: RESUME=UUID=4f94e345-f248-4150-a3e9-56cf8c64c3f9
  InstallationDate: Installed on 2016-05-10 (635 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 2QD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=c7c6075e-f6ef-4ab6-815c-625d09e8346c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (108 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J3IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16J3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J3IMS.111:bd01/12/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP622QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J3:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GP62 2QD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747321/+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 1747354] Re: Update bluez to version 5.48 in bionic

** Attachment added: "bluez_5.48-0ubuntu1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049023/+files/bluez_5.48-0ubuntu1.dsc

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747354] Re: Update bluez to version 5.48 in bionic

I can't remember which files are needed for a major upgrade so here's
everything.

** Tags added: bionic

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1746340] Re: Samsung SSD corruption (fsck needed)

So you have the issue on Linux v4.15 with
nvme_core.default_ps_max_latency_us=0, but not on v4.9?

APST doesn't get enabled on both of them.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb

[Kernel-packages] [Bug 1747354] Re: Update bluez to version 5.48 in bionic

** Attachment added: "bluez_5.48.orig.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049021/+files/bluez_5.48.orig.tar.xz

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747354] Re: Update bluez to version 5.48 in bionic

** Attachment added: "bluez_5.48-0ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049022/+files/bluez_5.48-0ubuntu1.debian.tar.xz

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747354] Re: Update bluez to version 5.48 in bionic

** Patch added: "bluez_5.48-0ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+attachment/5049020/+files/bluez_5.48-0ubuntu1.debdiff

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747354] [NEW] Update bluez to version 5.48 in bionic

Public bug reported:

Update bluez to version 5.48 in bionic

** Affects: bluez (Ubuntu)
 Importance: Wishlist
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1747336] Re: need linux-firmware for rtl bt ( 0bda:b023)

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  need linux-firmware for rtl bt ( 0bda:b023)

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

Bug description:
  rtl8822b_config.bin
  rtl8822b_fw.bin

  in the /lib/firmware/rtl_bt/

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1747336/+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 1736017] Re: trackpad looses sync and hangs -- 16.10 worked, 17.10 does not

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

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

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

Title:
  trackpad looses sync and hangs -- 16.10 worked, 17.10 does not

Status in linux package in Ubuntu:
  Expired

Bug description:
  I run Ubuntu 17.10 (Kubuntu) on a Thinkpad Yoga260 notebook. The
  trackpad hangs regularly, typically after a few minutes of use. dmesg
  reports "lost sync bytes".

  Interestingly, this error already occurred in 16.04 (there are many
  reports about this, e.g.
  https://askubuntu.com/questions/922092/lifebook-e546-touchpad-on-
  ubuntu-16-04), but my notebook works fine with 16.10 which I used for
  about a year without any problems. Now that I updated it to 17.10 it
  occurs again. Both 16.10 and 17.10 are now installed in parallel, but
  the error only manifests when I boot into the latter.

  I have tried proto=imps and proto=bare (module psmouse), but this does
  not make a difference.

  I report this here because this might be some kind of regression (or
  coincidence).

  Output from dmesg:

  The trackpad detected es one from elantech:
  [1.952397] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x4d1f04)
  [1.967272] psmouse serio1: elantech: Synaptics capabilities query result 
0x80, 0x14, 0x0c.
  [1.982603] psmouse serio1: elantech: Elan sample query result 04, 01, 85

  
  [  802.847308] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.854537] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.862926] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.870528] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.877890] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.877899] psmouse serio1: issuing reconnect request
  [  805.772533] psmouse serio1: elantech: PS/2 packet [54 80 80 36 00 00]
  [ 1008.218685] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.226641] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.234590] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.242843] psmouse serio1: elantech: PS/2 packet [75 31 52 96 44 19]
  [ 1008.242851] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver 
resynced.
  [ 1008.251339] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.258971] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.265958] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.273071] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.280932] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.280940] psmouse serio1: issuing reconnect request

  
  etc...
  --- 
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal 1282 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=cb84af7b-bfe3-432a-a69a-6a448b1f667a
  InstallationDate: Installed on 2017-12-01 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20FES2N100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=c07aafe2-3841-467a-becb-e8173c55fac4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET82W (1.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES2N100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET82W(1.61):bd09/30/2017:svnLENOVO:pn20FES2N100:pvrThinkPadYoga260:rvnLENOVO:rn20FES2N100:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES2N100
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO

[Kernel-packages] [Bug 1736709] Re: Ubuntu freezes

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

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

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

Title:
  Ubuntu freezes

Status in linux package in Ubuntu:
  Expired

Bug description:
  after a few minutes the system freezes

  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/controlC0:  eduardo1402 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 11:18:10 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=05f177d8-57e6-4f22-a793-8c7e1177d734
  InstallationDate: Installed on 2017-11-29 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3f45c6ca-b19f-4e2b-9165-90102026709a ro quiet splash vt.handoff=7
  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.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736709/+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 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

Turning core files into crash files after the fact is a bit too late in
my case. With Xwayland and gnome-shell both racing to write ~/core I
will still be missing one of them.

--

journalctl -u apport says:

...
-- Reboot --
Feb 05 12:01:27 haz systemd[1]: Starting LSB: automatic crash report 
generation...
Feb 05 12:01:27 haz apport[740]:  * Starting automatic crash report generation: 
apport
Feb 05 12:01:27 haz apport[740]:...done.
Feb 05 12:01:27 haz systemd[1]: Started LSB: automatic crash report generation.

--

$ cat /var/log/apport.log
ERROR: apport (pid 1657) Mon Feb  5 12:02:48 2018: called for pid 923, signal 
5, core limit 0, dump mode 1
ERROR: apport (pid 1657) Mon Feb  5 12:02:48 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 1657) Mon Feb  5 12:02:48 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 1657) Mon Feb  5 12:02:48 2018: debug: session gdbus call: 
ERROR: apport (pid 1657) Mon Feb  5 12:03:04 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.120.crash
ERROR: apport (pid 1946) Mon Feb  5 12:05:58 2018: another apport instance is 
already running, aborting
ERROR: apport (pid 1941) Mon Feb  5 12:05:55 2018: called for pid 1767, signal 
6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1941) Mon Feb  5 12:05:55 2018: ignoring implausibly big 
core limit, treating as unlimited
ERROR: apport (pid 1941) Mon Feb  5 12:05:55 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-core -listen 4 -listen 5 -displayfd 6")
ERROR: apport (pid 1941) Mon Feb  5 12:05:55 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 1941) Mon Feb  5 12:05:55 2018: debug: session gdbus call: 
ERROR: apport (pid 1941) Mon Feb  5 12:05:58 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
ERROR: apport (pid 1941) Mon Feb  5 12:05:58 2018: writing core dump to 
/home/dan/core (limit: -1)
ERROR: apport (pid 1941) Mon Feb  5 12:05:59 2018: writing core dump 
/home/dan/core of size 91402240

--

$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P


** Changed in: apport (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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic

[Kernel-packages] [Bug 1747336] [NEW] need linux-firmware for rtl bt ( 0bda:b023)

2018-02-04 Thread Hui Wang

Public bug reported:

rtl8822b_config.bin
rtl8822b_fw.bin

in the /lib/firmware/rtl_bt/

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: originate-from-1741423 sutton

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => Critical

** Tags added: originate-from-1741423 sutton

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

Title:
  need linux-firmware for rtl bt ( 0bda:b023)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  rtl8822b_config.bin
  rtl8822b_fw.bin

  in the /lib/firmware/rtl_bt/

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1747336/+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 1747307] Missing required logs.

2018-02-04 Thread 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 1747307

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

Title:
  Wi-Fi networks list is empty after resume from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  After the laptop has resumed from suspend, there are no Wi-Fi networks
  listed in the network manager applet. The connection still works but
  the applet shows the Ethernet connection icon.

  Steps to reproduce:
  1) close the laptop lid to enter suspend (or click "suspend" in the system 
menu in the upper panel)
  2) re-open the laptop lid, resuming the laptop from suspend, unlock the screen
  3) check the network manager applet, no Wi-Fi networks are listed, disabling 
and re-enabling Wi-Fi doesn't help

  This is a problem because it isn't possible to connect to another Wi-
  Fi network.

  The problem disappears if i run:

  sudo systemctl restart network-manager.service

  as described here: https://askubuntu.com/a/761220, however, the
  systemd unit file solution suggested in the same answer doesn't work,
  probably due to a timing issue (the command is run too early and the
  Wi-Fi card is not ready).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  4 22:55:37 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-01-30 (4 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.145  
metric 600 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747307/+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 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

@Mario,
Yea, it might be a hardware problem..

@Joseph
Good to know. So I'll close this issue then ;)


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

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

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745747/+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 1747307] Re: Wi-Fi networks list is empty after resume from suspend

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

Title:
  Wi-Fi networks list is empty after resume from suspend

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  After the laptop has resumed from suspend, there are no Wi-Fi networks
  listed in the network manager applet. The connection still works but
  the applet shows the Ethernet connection icon.

  Steps to reproduce:
  1) close the laptop lid to enter suspend (or click "suspend" in the system 
menu in the upper panel)
  2) re-open the laptop lid, resuming the laptop from suspend, unlock the screen
  3) check the network manager applet, no Wi-Fi networks are listed, disabling 
and re-enabling Wi-Fi doesn't help

  This is a problem because it isn't possible to connect to another Wi-
  Fi network.

  The problem disappears if i run:

  sudo systemctl restart network-manager.service

  as described here: https://askubuntu.com/a/761220, however, the
  systemd unit file solution suggested in the same answer doesn't work,
  probably due to a timing issue (the command is run too early and the
  Wi-Fi card is not ready).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  4 22:55:37 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-01-30 (4 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.145  
metric 600 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747307/+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 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

You just double-click on them and follow the instructions. If for some
reason that doesn't work then you can run 'dpkg -i '

Here are some new links that work:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-
headers-4.15.1-041501_4.15.1-041501.201802031831_all.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-
headers-4.15.1-041501-generic_4.15.1-041501.201802031831_amd64.deb

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.1/linux-
image-4.15.1-041501-generic_4.15.1-041501.201802031831_amd64.deb

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

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

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics

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

2018-02-04 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  randomly freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems to randomly freeze (mouse and keyboard) then, need to re-login and 
relaunch programs (what I was working on). Since it is random, do not know the 
cause.
  This report is sent immediately after the freeze/crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sheldon   10520 F pulseaudio
   /dev/snd/controlC1:  sheldon   10520 F pulseaudio
   /dev/snd/controlC0:  sheldon   10520 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 19:40:40 2018
  HibernationDevice: RESUME=UUID=4f94e345-f248-4150-a3e9-56cf8c64c3f9
  InstallationDate: Installed on 2016-05-10 (635 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 2QD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=c7c6075e-f6ef-4ab6-815c-625d09e8346c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (108 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J3IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16J3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J3IMS.111:bd01/12/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP622QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J3:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GP62 2QD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747321/+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 1747321] [NEW] randomly freezes

2018-02-04 Thread Sheldon Maschmeyer

Public bug reported:

It seems to randomly freeze (mouse and keyboard) then, need to re-login and 
relaunch programs (what I was working on). Since it is random, do not know the 
cause.
This report is sent immediately after the freeze/crash.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  sheldon   10520 F pulseaudio
 /dev/snd/controlC1:  sheldon   10520 F pulseaudio
 /dev/snd/controlC0:  sheldon   10520 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb  4 19:40:40 2018
HibernationDevice: RESUME=UUID=4f94e345-f248-4150-a3e9-56cf8c64c3f9
InstallationDate: Installed on 2016-05-10 (635 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Micro-Star International Co., Ltd. GP62 2QD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=c7c6075e-f6ef-4ab6-815c-625d09e8346c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic  N/A
 linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-20 (108 days ago)
dmi.bios.date: 01/12/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16J3IMS.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16J3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J3IMS.111:bd01/12/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP622QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J3:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: GP62 2QD
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

Title:
  randomly freezes

Status in linux package in Ubuntu:
  New

Bug description:
  It seems to randomly freeze (mouse and keyboard) then, need to re-login and 
relaunch programs (what I was working on). Since it is random, do not know the 
cause.
  This report is sent immediately after the freeze/crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sheldon   10520 F pulseaudio
   /dev/snd/controlC1:  sheldon   10520 F pulseaudio
   /dev/snd/controlC0:  sheldon   10520 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 19:40:40 2018
  HibernationDevice: RESUME=UUID=4f94e345-f248-4150-a3e9-56cf8c64c3f9
  InstallationDate: Installed on 2016-05-10 (635 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 2QD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=c7c6075e-f6ef-4ab6-815c-625d09e8346c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (108 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J3IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16J3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J3IMS.111:bd01/12/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP622QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J3:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GP62 2QD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-04 Thread gamdow

@fardin

Happy to hear you're making progress, though I won't be able to help you
as much at this stage because your system is setup up differently from
mine.

Since you've reached the initrmfs terminal, you just need to locate
"vmlinuz" now that the drives have been reordered. That should be
wherever the root of filesystem has been mounted (e.g. "/"). Thankfully
initrmfs will have all the basic functions of a standard terminal. So
try "lsblk" to list all the drives/partitions and their ids, and look
for the partition that has the "/" MOUNTPOINT. That should be the name
you use for the root in the second grub command.

Failing that, you could use other basic terminal commands like "ls
/dev", 'find / -name "vmlinuz"', etc. to figure out your particular
setup.

--
You 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:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
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

Bug description:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

1. Boot into Ubuntu
2. Download
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
3. Install the downloaded package:
$ sudo dpkg -i
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
4. Make sure the kernel is installed without any error. Once installed,
reboot.
5. At grub, choose the newly installed kernel. You can choose the "recovery"
mode.
6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
7. In case your BIOS is not recovered, reboot to the new kernel, then reboot
*once again* to the new kernel, do not enter BIOS settings before the reboot.
After the second reboot, check BIOS.
8. If your BIOS issue remains, download another kernel from
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
and use dpkg to install it, then repeat steps 4 to 6.

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

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.

---

Affected Machines:

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 Yoga 3 11"
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Toshiba Satellite L70-A-13M
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw, 0xef6015
w25q32dw, 0xef6016
w25q64dw, 0xef6017
w25q128fw, 0xef6018

---

Original Description:

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

[Kernel-packages] [Bug 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Christopher M. Penalver

Sergey Zolotarev, to clarify, let us focus on the timeframe from since
you installed Ubuntu a couple weeks ago to present.

1) To advise, it wouldn't hurt to see how things change when you use the
nvidia proprietary driver. However, you will want to use the Ubuntu
kernel (not mainline) before installing it and while using it. For
information on nvidia versions available one may see
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia .

2) To clarify, when you resume from suspend, is it that one of the three 
following outcomes occur or only two:
* Upon resume the display is not working and you can't SSH into it.
* It resumes but only the touchpad isn't working.
* It resumes and everything is working fine.

3) It would be helpful if you out the nvidia card from the pc to see if
this influences your resume results.

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746372/+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 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Sergey Zolotarev

I installed Ubuntu on this laptop a couple of weeks ago, so I can't say.
But before Ubuntu I was using Fedora 27 for around 2 months and I didn't
experience this problem there.

I'm attaching dmesg output after another touchpad incident, from 4.15.1
this time. I hope it helps. It looks like this may have something to do
with nouveau, should I try using the proprietary NVIDIA drivers?

** Attachment added: "dmesg2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746372/+attachment/5048856/+files/dmesg2.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/1746372

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746372/+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 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Christopher M. Penalver

Sergey Zolotarev, to clarify, have you always had the issue of the
display not working after waking up and you can't SSH into it, or is
this something that started recently?

** Tags added: latest-bios-300

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746372/+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 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Sergey Zolotarev

I've installed the 4.15.1 kernel, what should I do next? I'm having the
same pm_trace issue as before.

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746372/+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 1747293] Status changed to Confirmed

2018-02-04 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  randomly freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems to randomly freeze (mouse and keyboard) then, sometimes need
  to re-login and relaunch programs (i.e. Firefox & LibreOffice). Since
  it is random, do not know the cause.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sheldon   13044 F pulseaudio
   /dev/snd/controlC0:  sheldon   13044 F pulseaudio
   /dev/snd/controlC1:  sheldon   13044 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 14:24:33 2018
  HibernationDevice: RESUME=UUID=4f94e345-f248-4150-a3e9-56cf8c64c3f9
  InstallationDate: Installed on 2016-05-10 (634 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 2QD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=c7c6075e-f6ef-4ab6-815c-625d09e8346c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (107 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J3IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16J3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J3IMS.111:bd01/12/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP622QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J3:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GP62 2QD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747293/+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 1747293] [NEW] randomly freezes

2018-02-04 Thread Sheldon Maschmeyer

Public bug reported:

It seems to randomly freeze (mouse and keyboard) then, sometimes need to
re-login and relaunch programs (i.e. Firefox & LibreOffice). Since it is
random, do not know the cause.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  sheldon   13044 F pulseaudio
 /dev/snd/controlC0:  sheldon   13044 F pulseaudio
 /dev/snd/controlC1:  sheldon   13044 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb  4 14:24:33 2018
HibernationDevice: RESUME=UUID=4f94e345-f248-4150-a3e9-56cf8c64c3f9
InstallationDate: Installed on 2016-05-10 (634 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Micro-Star International Co., Ltd. GP62 2QD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=c7c6075e-f6ef-4ab6-815c-625d09e8346c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic  N/A
 linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-20 (107 days ago)
dmi.bios.date: 01/12/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16J3IMS.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16J3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J3IMS.111:bd01/12/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP622QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J3:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: GP62 2QD
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

Title:
  randomly freezes

Status in linux package in Ubuntu:
  New

Bug description:
  It seems to randomly freeze (mouse and keyboard) then, sometimes need
  to re-login and relaunch programs (i.e. Firefox & LibreOffice). Since
  it is random, do not know the cause.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sheldon   13044 F pulseaudio
   /dev/snd/controlC0:  sheldon   13044 F pulseaudio
   /dev/snd/controlC1:  sheldon   13044 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  4 14:24:33 2018
  HibernationDevice: RESUME=UUID=4f94e345-f248-4150-a3e9-56cf8c64c3f9
  InstallationDate: Installed on 2016-05-10 (634 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 2QD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=c7c6075e-f6ef-4ab6-815c-625d09e8346c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (107 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J3IMS.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16J3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J3IMS.111:bd01/12/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP622QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J3:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: GP62 2QD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working

2018-02-04 Thread TauSo

Unfortunately it's not working, but the bug is at another codeline, so
maybe another problem? Or the same problem is in the code multiple
times?

 [ cut here ]
[5.990508] kernel BUG at 
/home/khfeng/Sources/linux-lp1742316-saa7146/drivers/media/common/saa7146/saa7146_core.c:166!
[5.990519] invalid opcode:  [#1] SMP
[5.990521] Modules linked in: ppdev snd_hda_codec_realtek(+) 
snd_hda_codec_generic budget_av(+) saa7146_vv snd_hda_intel budget_core 
ttpci_eeprom snd_hda_codec saa7146 snd_hda_core videobuf_dma_sg videobuf_core 
snd_hwdep dvb_core snd_pcm v4l2_common snd_timer videodev snd intel_powerclamp 
joydev media lpc_ich input_leds soundcore shpchp parport_pc nuvoton_cir parport 
rc_core mac_hid nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 
hid_generic usbhid hid gma500_gfx i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt r8169 ahci fb_sys_fops drm libahci mii video
[5.990587] CPU: 1 PID: 301 Comm: systemd-udevd Not tainted 
4.13.0-33-generic #36
[5.990589] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./AD2700-ITX, BIOS P1.60 04/19/2013
[5.990591] task: f49bf500 task.stack: f4986000
[5.990601] EIP: saa7146_vmalloc_build_pgtable+0x188/0x1020 [saa7146]
[5.990603] EFLAGS: 00010246 CPU: 1
[5.990605] EAX: f1ce7d88 EBX: f8236000 ECX: 0002 EDX: fff1c000
[5.990608] ESI:  EDI: f84f2000 EBP: f4987c44 ESP: f4987c20
[5.990610]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[5.990613] CR0: 80050033 CR2: b7b6715c CR3: 34935d60 CR4: 06f0
[5.990615] Call Trace:
[5.990627]  ttpci_budget_init+0x26c/0x530 [budget_core]
[5.990637]  budget_av_attach+0x75/0x4e8 [budget_av]
[5.990646]  ? vprintk_func+0x29/0x70
[5.990650]  ? printk+0x13/0x15
[5.990655]  ? saa7146_init_one+0x69f/0x770 [saa7146]
[5.990661]  saa7146_init_one+0x70b/0x770 [saa7146]
[5.990667]  ? __pm_runtime_resume+0x51/0x80
[5.990673]  pci_device_probe+0xc2/0x160
[5.990679]  driver_probe_device+0x2b9/0x410
[5.990683]  __driver_attach+0x99/0xe0
[5.990687]  ? driver_probe_device+0x410/0x410
[5.990691]  bus_for_each_dev+0x57/0x90
[5.990695]  driver_attach+0x19/0x20
[5.990698]  ? driver_probe_device+0x410/0x410
[5.990702]  bus_add_driver+0x187/0x230
[5.990705]  ? 0xf826e000
[5.990709]  driver_register+0x56/0xd0
[5.990712]  ? 0xf826e000
[5.990715]  __pci_register_driver+0x33/0x40
[5.990721]  saa7146_register_extension+0x50/0x80 [saa7146]
[5.990730]  budget_av_init+0xd/0x1000 [budget_av]
[5.990735]  do_one_initcall+0x46/0x180
[5.990741]  ? vunmap_page_range+0x13e/0x280
[5.990746]  ? kvfree+0x45/0x50
[5.990750]  ? kmem_cache_alloc_trace+0x13d/0x1a0
[5.990754]  ? do_init_module+0x21/0x1cc
[5.990758]  ? do_init_module+0x21/0x1cc
[5.990762]  do_init_module+0x50/0x1cc
[5.990765]  load_module+0x1533/0x1aa0
[5.990772]  ? kernel_read_file+0x26e/0x2a0
[5.990778]  SyS_finit_module+0x8a/0xe0
[5.990785]  do_fast_syscall_32+0x71/0x150
[5.990791]  entry_SYSENTER_32+0x4e/0x7c
[5.990794] EIP: 0xb7f5acf9
[5.990795] EFLAGS: 0296 CPU: 1
[5.990798] EAX: ffda EBX: 0018 ECX: b7d4ba71 EDX: 
[5.990800] ESI: 0241e980 EDI: 02417940 EBP:  ESP: bffc10ac
[5.990803]  DS: 007b ES: 007b FS:  GS: 0033 SS: 007b
[5.990806] Code: e8 e8 bd eb ff ff 85 c0 59 75 7c 8b 45 ec 8d 65 f4 5b 5e 
5f 5d c3 90 8d 74 26 00 83 3d f0 ec e1 d3 02 0f 85 0c ff ff ff 8d 76 00 <0f> 0b 
8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 c7 45 dc 00 00
[5.990875] EIP: saa7146_vmalloc_build_pgtable+0x188/0x1020 [saa7146] 
SS:ESP: 0068:f4987c20
[5.990879] ---[ end trace b40ecb3f8210604e ]---

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c',

[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-02-04 Thread Gopal

System:Host: gopal-HP-Notebook Kernel: 4.15.0-041500-generic x86_64 (64 bit 
gcc: 7.2.0)
   Desktop: Unity 7.4.0 (Gtk 3.18.9-1ubuntu3.3) dm: lightdm
   Distro: Ubuntu 16.04 xenial
Machine:   System: HP product: HP Notebook v: Type1ProductConfigId
   Mobo: HP model: 81EC v: 61.58 Bios: Insyde v: F.40 date: 11/01/2017
   Chassis: type: 10
CPU:   Dual core Intel Core i5-6200U (-HT-MCP-) cache: 3072 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9600
   clock speeds: min/max: 400/2800 MHz 1: 987 MHz 2: 547 MHz
   3: 567 MHz 4: 541 MHz
Graphics:  Card-1: Intel Sky Lake Integrated Graphics
   bus-ID: 00:02.0 chip-ID: 8086:1916
   Card-2: Advanced Micro Devices [AMD/ATI] Sun XT [Radeon HD 
8670A/8670M/8690M / R5 M330]
   bus-ID: 01:00.0 chip-ID: 1002:6660
   Display Server: X.Org 1.19.5 drivers: (unloaded: fbdev,vesa)
   Resolution: 1366x768@60.02hz
   GLX Renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
   GLX Version: 3.0 Mesa 17.2.4 Direct Rendering: Yes
Audio: Card Intel Sunrise Point-LP HD Audio
   driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:9d70
   Sound: Advanced Linux Sound Architecture v: k4.15.0-041500-generic
Network:   Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
controller
   driver: r8169 v: 2.3LK-NAPI port: 3000
   bus-ID: 02:00.0 chip-ID: 10ec:8136
   IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 
   Card-2: Broadcom BCM43142 802.11b/g/n
   bus-ID: 03:00.0 chip-ID: 14e4:4365
   IF: N/A state: N/A mac: N/A
Drives:HDD Total Size: 120.0GB (4.7% used)
   ID-1: /dev/sda model: ADATA_SP580 size: 120.0GB serial: 
H30276K015977 temp: 43C
Partition: ID-1: / size: 110G used: 5.3G (6%) fs: ext4 dev: /dev/sda1
RAID:  System: supported: N/A
   No RAID devices: /proc/mdstat, md_mod kernel module present
   Unused Devices: none
Sensors:   System Temperatures: cpu: 37.0C mobo: 29.8C
   Fan Speeds (in rpm): cpu: N/A
Repos: Active apt sources in file: /etc/apt/sources.list
   deb http://in.archive.ubuntu.com/ubuntu/ xenial main restricted
   deb http://in.archive.ubuntu.com/ubuntu/ xenial-updates main 
restricted
   deb http://in.archive.ubuntu.com/ubuntu/ xenial universe
   deb http://in.archive.ubuntu.com/ubuntu/ xenial-updates universe
   deb http://in.archive.ubuntu.com/ubuntu/ xenial multiverse
   deb http://in.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
   deb http://in.archive.ubuntu.com/ubuntu/ xenial-backports main 
restricted universe multiverse
   deb http://security.ubuntu.com/ubuntu xenial-security main restricted
   deb http://security.ubuntu.com/ubuntu xenial-security universe
   deb http://security.ubuntu.com/ubuntu xenial-security multiverse
Info:  Processes: 202 Uptime: 1:42 Memory: 1059.6/11900.5MB
   Init: systemd v: 229 runlevel: 5 default: 2 Gcc sys: 5.4.0
   Client: Shell (bash 4.3.481 running in gnome-terminal-) inxi: 2.2.35

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003:

[Kernel-packages] [Bug 1746232] Re: driver looping then crashing

2018-02-04 Thread Roger James

I have raised this bug at
https://bugzilla.kernel.org/show_bug.cgi?id=198669

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

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

Title:
  driver looping then crashing

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

Bug description:
  Running driver on Artful with the xwayland compositor. At random times
  the GPU stalls with.

  Jan 30 11:22:28 dragon kernel: [  487.046219] radeon :02:00.0: ring 0 
stalled for more than 29200msec
  Jan 30 11:22:28 dragon kernel: [  487.046224] radeon :02:00.0: GPU lockup 
(current fence id 0x1bdb last fence id 0x1bdc on ring 0)

  Usually when the system is idle.

  The above message is repeated once a second for a while. This usually
  but not always terminates with a page load fault in the driver.

  System can run for a few days without this happening. But on average
  it is once or twice a day.


  
  Jan 30 11:22:30 dragon kernel: [  488.507091] BUG: unable to handle kernel 
paging request at b406c1891ffc
  Jan 30 11:22:30 dragon kernel: [  488.507176] IP: 
radeon_ring_backup+0xd3/0x140 [radeon]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-video-radeon 1:7.10.0-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 30 11:40:08 2018
  DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] 
[1002:9442] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-07-01 (577 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/wd-root ro
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Dec  9 13:32:35 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746372] Re: [Asus K501UQ] Touchpad stops working after suspend

2018-02-04 Thread Christopher M. Penalver

Sergey Zolotarev, the latest mainline kernel is now 4.15.1. As per your
logs, you were booted in the Ubuntu kernel. So that upstream may review,
could you please provide the information with latest mainline?

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

Title:
  [Asus K501UQ] Touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When Ubuntu wakes up after suspend the touchpad doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  szx1685 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 31 05:40:49 2018
  InstallationDate: Installed on 2018-01-23 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=04181349-688b-425f-899c-822fcf6a409b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UQ.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UQ.300:bd09/13/2016:svnASUSTeKCOMPUTERINC.:pnK501UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K501UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746372/+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 1742316] Re: DVB Card with SAA7146 chipset not working

Hmm I think my previous kernel won't work because your system is 32bit.
I'll build a new one soon.

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/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: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Wed Jan 10 00:42:24 2018
  HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456
  InstallationDate: Installed on 2016-02-13 (696 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 
(20151021)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force 
video=LVDS-1:d vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago)
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: AD2700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742316/+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 1742316] Re: DVB Card with SAA7146 chipset not working

Please try this kernel,
http://people.canonical.com/~khfeng/lp1742316-i386-2/

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/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: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Wed Jan 10 00:42:24 2018
  HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456
  InstallationDate: Installed on 2016-02-13 (696 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 
(20151021)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force 
video=LVDS-1:d vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago)
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: AD2700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742316/+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 1747263] Re: [artful] panic in update_stack_state when reading /proc//stack on i386

2018-02-04 Thread Andy Whitcroft

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

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

Title:
  [artful] panic in update_stack_state when reading /proc//stack on
  i386

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It seems that when reading /proc//stack we can sometimes triggers
  a panic on i386.  This is triggered by an unsafe pointer access when
  validating the stack in the stack unwinder.  This is reproducible in a
  4 cpu 32bit VM with the stress-ng /proc stressor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747263/+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 1747263] Re: [artful] panic in update_stack_state when reading /proc//stack on i386

2018-02-04 Thread Andy Whitcroft

The below commit has been confirmed as the fix for this:

commit 62dd86ac01f9fb6386d7f8c6b389c3ea4582a50a
Author: Josh Poimboeuf 
Date:   Mon Oct 9 20:20:02 2017 -0500

x86/unwind: Fix dereference of untrusted pointer

Tetsuo Handa and Fengguang Wu reported a panic in the unwinder:

  BUG: unable to handle kernel NULL pointer dereference at 01f2
  IP: update_stack_state+0xd4/0x340
  *pde = 

  Oops:  [#1] PREEMPT SMP
  CPU: 0 PID: 18728 Comm: 01-cpu-hotplug Not tainted 
4.13.0-rc4-00170-gb09be67 #592
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.9.3-20161025_171302-gandalf 04/01/2014
  task: bb0b53c0 task.stack: bb3ac000
  EIP: update_stack_state+0xd4/0x340
  EFLAGS: 00010002 CPU: 0
  EAX: a570 EBX: bb3adccb ECX: f401 EDX: a570
  ESI: 0001 EDI: 01ba EBP: bb3adc6b ESP: bb3adc3f
   DS: 007b ES: 007b FS: 00d8 GS:  SS: 0068
  CR0: 80050033 CR2: 01f2 CR3: 0b3a7000 CR4: 00140690
  DR0:  DR1:  DR2:  DR3: 
  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   ? unwind_next_frame+0xea/0x400
   ? __unwind_start+0xf5/0x180
   ? __save_stack_trace+0x81/0x160
   ? save_stack_trace+0x20/0x30
   ? __lock_acquire+0xfa5/0x12f0
   ? lock_acquire+0x1c2/0x230
   ? tick_periodic+0x3a/0xf0
   ? _raw_spin_lock+0x42/0x50
   ? tick_periodic+0x3a/0xf0
   ? tick_periodic+0x3a/0xf0
   ? debug_smp_processor_id+0x12/0x20
   ? tick_handle_periodic+0x23/0xc0
   ? local_apic_timer_interrupt+0x63/0x70
   ? smp_trace_apic_timer_interrupt+0x235/0x6a0
   ? trace_apic_timer_interrupt+0x37/0x3c
   ? strrchr+0x23/0x50
  Code: 0f 95 c1 89 c7 89 45 e4 0f b6 c1 89 c6 89 45 dc 8b 04 85 98 cb 74 
bc 88 4d e3 89 45 f0 83 c0 01 84 c9 89 04 b5 98 cb 74 bc 74 3b <8b> 47 38 8b 57 
34 c6 43 1d 01 25 00 00 02 00 83 e2 03 09 d0 83
  EIP: update_stack_state+0xd4/0x340 SS:ESP: 0068:bb3adc3f
  CR2: 01f2
  ---[ end trace 0d147fd4aba8ff50 ]---
  Kernel panic - not syncing: Fatal exception in interrupt

On x86-32, after decoding a frame pointer to get a regs address,
regs_size() dereferences the regs pointer when it checks regs->cs to see
if the regs are user mode.  This is dangerous because it's possible that
what looks like a decoded frame pointer is actually a corrupt value, and
we don't want the unwinder to make things worse.

Instead of calling regs_size() on an unsafe pointer, just assume they're
kernel regs to start with.  Later, once it's safe to access the regs, we
can do the user mode check and corresponding safety check for the
remaining two regs.

Reported-and-tested-by: Tetsuo Handa 
Reported-and-tested-by: Fengguang Wu 
Signed-off-by: Josh Poimboeuf 
Cc: Byungchul Park 
Cc: LKP 
Cc: Linus Torvalds 
Cc: Peter Zijlstra 
Cc: Thomas Gleixner 
Fixes: 5ed8d8bb38c5 ("x86/unwind: Move common code into 
update_stack_state()")
Link: 
http://lkml.kernel.org/r/7f95b9a6993dec7674b3f3ab3dcd3294f7b9644d.1507597785.git.jpoim...@redhat.com
Signed-off-by: Ingo Molnar 

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

Title:
  [artful] panic in update_stack_state when reading /proc//stack on
  i386

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It seems that when reading /proc//stack we can sometimes triggers
  a panic on i386.  This is triggered by an unsafe pointer access when
  validating the stack in the stack unwinder.  This is reproducible in a
  4 cpu 32bit VM with the stress-ng /proc stressor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747263/+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 1747263] [NEW] [artful] panic in update_stack_state when reading /proc//stack on i386

2018-02-04 Thread Andy Whitcroft

Public bug reported:

It seems that when reading /proc//stack we can sometimes triggers a
panic on i386.  This is triggered by an unsafe pointer access when
validating the stack in the stack unwinder.  This is reproducible in a 4
cpu 32bit VM with the stress-ng /proc stressor.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: In Progress

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

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

Title:
  [artful] panic in update_stack_state when reading /proc//stack on
  i386

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It seems that when reading /proc//stack we can sometimes triggers
  a panic on i386.  This is triggered by an unsafe pointer access when
  validating the stack in the stack unwinder.  This is reproducible in a
  4 cpu 32bit VM with the stress-ng /proc stressor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747263/+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 1745646] Re: Battery drains when laptop is off (shutdown)

2018-02-04 Thread Gopal

https://bugzilla.kernel.org/show_bug.cgi?id=198665

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

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  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.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745646/+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 1547332] [NEW] [Feature Request] Provide option to install root to a ZFS formatted disk

You have been subscribed to a public bug by costinel (costinel):

Now that ZFS tools and support will be included by default in 16.04, it
would be great if we could install directly to a ZFS formatted disk
using the graphical installer.

Yes, I know that root can be manually installed to ZFS formated disk.
See https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-install-Ubuntu-to-a
-Native-ZFS-Root-Filesystem  But an option to install using the
graphical installer would be nice.

** Affects: ubiquity (Ubuntu)
 Importance: Wishlist
 Status: Confirmed


** Tags: xenial
-- 
 [Feature Request] Provide option to install root to a ZFS formatted disk
https://bugs.launchpad.net/bugs/1547332
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to the bug report.

-- 
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 1708409] Re: kdump service does not start after configure/reboot

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  In Progress
Status in makedumpfile source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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 1734172] Re: Upgrade ZFS to 0.7.3

2018-02-04 Thread costinel

@ comment #9, it has landed into proposed, not into main! this means
xenial won't get 0.7 via hwe... :(

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

Title:
  Upgrade ZFS to 0.7.3

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  ZFS v0.7 is out, current version is 0.7.3:

  https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.3 .

  
  It is desired to have the latest stable version at least in LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfsutils-linux 0.6.5.11-1ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  Date: Thu Nov 23 19:03:47 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (187 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1734172/+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 1744852] Re: Broken screen at kernel 4.13.0-32 (16.04 HWE)

2018-02-04 Thread la Nube

After Upgrading kernel 4.15.1, also Works WELL.

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

Title:
  Broken screen at kernel 4.13.0-32 (16.04 HWE)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded linux kernel from 4.10.0-42.46~16.04.1 to 4.13.0-31.34~16.04.1.
  After rebooting, my linux screen has been broken.

  See Imgur images.

  https://i.imgur.com/9cXTyIG.jpg
  https://i.imgur.com/0skgISl.jpg

  Restroing kernel 4.10, then works well.
  Also, 4.4.0-112.135 works well.

  --

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.3 LTS
  Release: 16.04
  Codename: xenial
  Linux asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 
UTC 2017 i686 i686 i686 GNU/Linux

  CPU: Single core Intel Atom N270 (-HT-) cache: 512 KB
     flags: (nx pae sse sse2 sse3 ssse3) bmips: 3192
     clock speeds: max: 1600 MHz 1: 1333 MHz 2: 800 MHz

  Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller
     bus-ID: 00:02.0
     Display Server: N/A drivers: intel (unloaded: fbdev,vesa)
     tty size: 80x24 Advanced Data: N/A out of X

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744852/+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 1746340] Re: Samsung SSD corruption (fsck needed)

Problem persists with 4.15.0-041500-generic, just happened

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)