date:20180812

[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/1776325

Title:
  Error messages during boot - Ubuntu 18.04 & Mint19

Status in linux package in Ubuntu:
  Expired

Bug description:
  This came about as I had problems with efi while installing a dual
  boot of ubuntu and linux mint.

  As I understand it, during the boot process, the kernel sees a cpu
  count for the processor chip , AMD Ryzen 2400G, as 8 but 4 of them are
  graphics compute units. A little later in the process, the graphics
  processors cause errors.

  Subsequent to discovering this , I have added a line to grub
  GRUB_CMDLINE_LINUX_ which appears to have improved the boot process.
  It is 'ruc_nocbs=0-3'. The alteration in grub seems to help limit the
  cpu count and gets the boot process over the bump.

  I searched the interweb for clues and this seems to be a successful
  experiment. I am reporting this because I could not find any pertinent
  reference to this sort of problem with this particular chip. This
  search was not exhaustive so I hope I am not wasting your time :)

  I am attaching a file of concatenated system info for kernel reports
  as the options on this page only appear to allow one file to be
  selected
  (https://bugs.launchpad.net/ubuntu/+source/linux/+filebug/4aca6a90-6dc0-11e8
  -b34a-002481e7f48a.

   Most of this was my lack of understanding the efi requirements, but
  the lack of useful information in the Gigabyte motherboard manual
  about how the UEFI operation was managed by its operating system
  prolonged my agony.:)

  I hope this helps, thank you and keep up the fantastic work
  Bob.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tpf1528 F pulseaudio
   /dev/snd/controlC0:  tpf1528 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 12 09:38:39 2018
  HibernationDevice: RESUME=UUID=150c1cd8-2246-4c18-b40e-dc07d8425777
  InstallationDate: Installed on 2018-06-10 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=36d43481-0720-4808-a234-82941b71f750 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23d
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776325/+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 1776407] Re: intel_do_flush_locked failed:Bad address

[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/1776407

Title:
  intel_do_flush_locked failed:Bad address

Status in linux package in Ubuntu:
  Expired

Bug description:
  when my app run on about 3 days, it exits and throws error info:
  "intel_do_flush_locked failed:bad address". this information is
  throwed by OpenGL(mesa).

  relations: app -> SDL -> OpenGL(mesa) -> libdrm -> kernel
  frequency: often

  
  kernel version:Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17GNU/Linux
  meas version: 17.2.8
  libdrm : 2.4.83

  
  I think it is a kernel bug because the bad address is meaning error code 
"-EFALUT".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776407/+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 1776108] Re: Resume after hibernate/suspend fails

[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/1776108

Title:
  Resume after hibernate/suspend fails

Status in linux package in Ubuntu:
  Expired

Bug description:
  Fresh/clean install of 18.04 resulted in hibernation working (after it
  being broken on an upgrade install). Now after rebooting after recent
  package upgrades (last 4-5 days) resuming from suspend/hibernate
  fails. Have to force hard reboot

  Last message in syslog is: PM: suspend entry (deep)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  petter 1475 F pulseaudio
   /dev/snd/controlC0:  petter 1475 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 22:34:32 2018
  HibernationDevice: RESUME=UUID=8f436028-c350-445e-85dc-115d58d47796
  InstallationDate: Installed on 2018-05-18 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=bc80c3a6-55ef-4636-ac7a-d7bd837b6320 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776108/+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 1776592] Re: error: snapshot dump failed

[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/1776592

Title:
  error: snapshot dump failed

Status in linux package in Ubuntu:
  Expired

Bug description:
  To start live migration using LXD in docker my experimental setup is
  as follows:


  
  Physical machine OS: Ubuntu 16.04
  Docker version 17.06.0-ce, build 02c1d87
  lxc --version 2.0.11
  lxd --version 2.0.11
  criu --version Version: 2.6

  After successful installation of container named 'c1' i run the
  following command to save the current states of the container to disk:

   sudo lxc snapshot c1 checkpoint-2 --stateful

   But it gives following errors:
  error: snapshot dump failed
  (00.260241) Error (criu/sk-netlink.c:73): The socket has data to read
  (00.260268) Error (criu/cr-dump.c:1313): Dump files (pid: 9158) failed with -1
  (00.303791) Error (criu/cr-dump.c:1628): Dumping FAILED.

  
  Any, help will be appreciated. Solutions can be emailed directly at: 
adityaf...@gmail.com

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 [modified: 
boot/vmlinuz-4.13.0-36-generic]
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Jun 13 10:07:04 2018
  InstallationDate: Installed on 2018-06-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776592/+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 1786669] Re: Xorg freeze / nvidia-driver-390 does not boot

2018-08-12 Thread Daniel van Vugt

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Tags added: nvidia

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

Title:
  Xorg freeze / nvidia-driver-390 does not boot

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu installed in legacy mode (efi not supported)
  graphic card: Nvidia GF108 [GeForce GT 520]
  Kernel: linux-image-4.15.0-30-generic

  With default driver active [xserver-xorg-video-nouveau] the
  performance is reduced (compared to active nvidia driver in previous
  16.04 installation). Running games often leads to screen freeze (hard
  reboot necessary).

  On the other hand proprietary drivers do not work properly:
  1) with nvidia-driver-390 the system locks before showing gdm login (bad 
chars shown) with last kernel;
  2) with nvidia-driver-390 the screen is forced to 680x480 res using kernel 
linux-image-4.15.0-23-generic; also LAN/internet does not work;
  3) with nvidia-340 the monitor switches off during boot and the boot does not 
continue;

  Also tried to activate the nvidia ppa (ppa:graphics-drivers/ppa) to
  try the legacy driver (304), but I can't since it breaks several other
  packages.

  Googling around my guess either is for bugs in kernels from 4.15.0-23
  or for signed modules not working without efi.

  Thanks for your support!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompizPlugins: 
[core,composite,opengl,decor,regex,compiztoolbox,move,resize,imgpng,place,animation,expo,grid,vpswitch,mousepoll,workarounds,snap,gnomecompat,unitymtgrabhandles,session,ezoom,wall,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 12 09:34:04 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2018-08-08 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=6a0b9e44-0c07-4365-bdbb-a6a9ac7f88bd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A55-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd08/31/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1786669/+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 1786395] Re: Bluetooth will not search on 16.04 lts

2018-08-12 Thread Daniel van Vugt

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

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

Title:
  Bluetooth will not search on 16.04 lts

Status in bluez package in Ubuntu:
  New

Bug description:
  My computer can be found by other devices, when its discoverable in
  bluetooth but it will not search from the pc side. . My pc is an asus
  vivobook max with realtek simi conductor.

  after running the command below i get this

  sudo service bluetooth status

   bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Thu 2018-08-09 22:16:18 CDT; 37min ago
   Docs: man:bluetoothd(8)
   Main PID: 898 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─898 /usr/lib/bluetooth/bluetoothd

  Aug 09 22:16:19 Shaferos-X541NA bluetoothd[898]: Not enough free handles to 
register service
  Aug 09 22:16:19 Shaferos-X541NA bluetoothd[898]: Sap driver initialization 
failed.
  Aug 09 22:16:19 Shaferos-X541NA bluetoothd[898]: sap-server: Operation not 
permitted (1)
  Aug 09 22:16:37 Shaferos-X541NA bluetoothd[898]: Endpoint registered: 
sender=:1.35 path=/MediaEndpoint/A2DPSource
  Aug 09 22:16:37 Shaferos-X541NA bluetoothd[898]: Endpoint registered: 
sender=:1.35 path=/MediaEndpoint/A2DPSink
  Aug 09 22:17:23 Shaferos-X541NA bluetoothd[898]: Endpoint registered: 
sender=:1.69 path=/MediaEndpoint/A2DPSource
  Aug 09 22:17:23 Shaferos-X541NA bluetoothd[898]: Endpoint registered: 
sender=:1.69 path=/MediaEndpoint/A2DPSink
  Aug 09 22:17:23 Shaferos-X541NA bluetoothd[898]: RFCOMM server failed for 
Headset Voice gateway: rfcomm_bind: Address already in use (98)
  Aug 09 22:17:29 Shaferos-X541NA bluetoothd[898]: Endpoint unregistered: 
sender=:1.35 path=/MediaEndpoint/A2DPSource
  Aug 09 22:17:29 Shaferos-X541NA bluetoothd[898]: Endpoint unregistered: 
sender=:1.35 path=/MediaEndpoint/A2DPSink
  ~
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2018-07-22 (19 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 2386:310a  
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541NA
  Package: bluez 5.37-0ubuntu5.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=bbc2a3c0-f12e-403e-bd44-fb94514d1b90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
  Tags:  xenial
  Uname: Linux 4.15.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/17/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541NA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541NA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541NA.303:bd03/17/2017:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541NA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 3C:95:09:13:C9:D5  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN ISCAN 
RX bytes:1417 acl:0 sco:0 events:154 errors:0
TX bytes:28248 acl:0 sco:0 commands:154 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1786395/+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 1771245] Re: [ICL] Touch support

2018-08-12 Thread quanxian

this is ICL platform which not published, could not be public now.

** Information type changed from Public to Private

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

Title:
  [ICL] Touch support

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

Bug description:
  Description:

  Icelake is using for touch screen USB2 and I2C.
  Precise touch will be via SPI.

  Up to 2 independent screens
  Pen Report Rate: 300Hz
  Active pen latency <20ms
  BL impact < 5%

  Target Kernel:4.19
  Target Release: 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771245/+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 1228263] Re: Volume control doesn't work automatically when connecting Bluetooth device.

2018-08-12 Thread Daniel van Vugt

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Wishlist

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

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

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

Title:
  Volume control doesn't work automatically when connecting Bluetooth
  device.

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect a Bluetooth device, sound is automatically forwarded to
  the device but volume controls still control the internal sound card
  device.  I must open the sound settings and click on the Bluetooth
  output device to use volume controls.

  I wish that the volume controls would automatically control whatever
  output device is actually active. :)

  This bug has existed for many versions of Ubuntu now.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-25 (746 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterestingModules: btusb bluetooth
  MachineType: TOSHIBA TECRA R950
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=c7679e9c-34aa-4c9b-8e58-05ec7b8e4f63 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Tags:  xenial
  Uname: Linux 4.4.0-130-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo 
vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 10/01/2012
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 6.40
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA R950
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnTECRAR950:pvrPT530U-00T007:rvnTOSHIBA:rnTECRAR950:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA R950
  dmi.product.version: PT530U-00T007
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C8:F7:33:2D:6B:6B  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING 
RX bytes:580 acl:0 sco:0 events:31 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2018-05-24T08:46:03.060208
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1228263/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Yes, can I send you my email in PM in some way from here?

BTW, I've made a fresh install of 18.04 with irvs params.

dmesg looks really different with the kernel : (uploaded on jsfiddle as
you can see the RED lines quickly)

with default 4.15 kernel : https://jsfiddle.net/qg34bury/
with last 4.18.0 kernel : https://jsfiddle.net/pkchrt6n/

I didnt installed amdgpu pro... Don't know how and I guess it's not
really necessary as all is working good. (dont need nomodeset or
anything and no crash)

and there is my TEMPS after 30 mins at low usage :
https://prnt.sc/khu5dy

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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)

2018-08-12 Thread Lucas Zanella

Hi hariprasad. If possible, you could try our patched kernel which
disables ASPM:  https://people.canonical.com/~khfeng/pm961-disable-
aspm/. It worked for me but only when I added the nvme-
core.default_ps_max_latency_us=1500 kernel parameter. Maybe you can try
some day. We're still investigating the issue. When Kai Heng send me the
patch I can try it and see what changes.

-- 
You 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 1777238] Re: video lag

2018-08-12 Thread Boris

Hi Zoltan.  This computer (HP Envy 17 Leap Motion SE) is a fresh install
of 18.04.  I upgraded my Dell Inspiron from 16.04 and don't have the
issue.  Very weird.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-08-12 Thread Layke

So I was able to get everything working on 16.04 with nvidia-384. I
tried many a different things on 18.04 with nvidia-390 and nvidia-396
but no luck including using proposed Bionic Beaver but no luck. If I can
help report anything though I'd be glad to post it if you tell me what
you need from my system. I hope this bug is fixed soon. 18.04 LTS is an
improvement on 16.04 LTS I thought from my brief exposure to the system.
This setup seems to run slower compared to Bionic Beaver.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

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

2018-08-12 Thread Zoltán Süle

the situation is much better after unchecking v-sync, but still not
perfect.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

2018-08-12 Thread Christopher M. Penalver

whl2:

1) The latest mainline kernel is now 4.18 (not 4.18-rc). Could
you please advise to this?

2) When using 16.04, did you use 3rd party fan software or was it a
default install?

3) To further narrow down the regression, could you please test 4.4.5
and respond with the 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/1775717

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

Status in linux package in Ubuntu:
  Incomplete

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

  Things tried:

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

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

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

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

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

2018-08-12 Thread Zoltán Süle

Thanks Boris! The video was taken in 2012, but I experience these kind of 
problems since the upgrade from 16.04 to 18.04.
I had 10.04, 12.04 and 16.04 before without these issues.

I experience more problems with the kernel 4.15.0-30 and it looks much
better with kernel 4.17.0-x. Some upgrades make it better, some upgrades
make it worse.

I also run a Debian test system without these issues.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-08-12 Thread Richard Baka

I'm glad you did it. 
Why does the kernel not find the correct addres like lspci? This is a good 
question. Maybe the kernel doesn't know what to search.
I have a somewhat fixed (not perfectly) DSDT/SSDT for A315-41G (Ryzen 5 + 
Radeon vega 8/Radeon 535) which provides a better cpu power management(CPU 
temperature can decrease under 50C) like using the kernel  parameter only. If 
you send me a mail I can give it to you but I don't guarantee an error-free 
behavior.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

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

2018-08-12 Thread Boris

After posting the above, I found
https://www.youtube.com/watch?v=cIQZv6MXzno.

The first solution (uncheking v-sync, log out, log in) seems to be
working.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

2018-08-12 Thread Boris

The lag is everywhere for me, not just in video.  Screen scrolling also
has this stutter.

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

Title:
  video lag

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1786713] Re: MODULE_SOFTDEP for crc32c is not working

2018-08-12 Thread Tim Ritberg

there are no logs.

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

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

Title:
  MODULE_SOFTDEP for crc32c is not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a kernel config with Ext4, for which softdep is not working.
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265

  Ubuntu 18.04.
  Kernel 4.17.18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786713/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Ok. It start well with "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2" I
probably didnt writed right the first time... (ps)

It seems a good solution as my touchpad is working and my specials keys
too... (but as lscpi is capable to find addresses, I don't know why the
kernel couldnt find it by is own too. Anyway, I don't have enough
knowledges at all for all of this.)

Thanks for your help. I hope it could help more people with this
hardware.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Hi. 
Thanks for your precious informations.

I start with noapic and there is the lspci output :
https://paste.ubuntu.com/p/jm8MBy4qND/

Obviously I can see the same values as you for iommu (0:00.2)... So I'll
try to reboot again with "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2"
instead of "quiet splash".

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

2018-08-12 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 1786713

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

Title:
  MODULE_SOFTDEP for crc32c is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a kernel config with Ext4, for which softdep is not working.
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265

  Ubuntu 18.04.
  Kernel 4.17.18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786713/+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 1786713] [NEW] MODULE_SOFTDEP for crc32c is not working

2018-08-12 Thread Tim Ritberg

Public bug reported:

I have a kernel config with Ext4, for which softdep is not working. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265

Ubuntu 18.04.
Kernel 4.17.18

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


** Tags: ext4

** Attachment added: "config.txt"
   https://bugs.launchpad.net/bugs/1786713/+attachment/5174551/+files/config.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/1786713

Title:
  MODULE_SOFTDEP for crc32c is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a kernel config with Ext4, for which softdep is not working.
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778265

  Ubuntu 18.04.
  Kernel 4.17.18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786713/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-08-12 Thread Richard Baka

No sorry, instead of pci=noacpi, try to start the kernel with noapic and
then check lspci. It there is a kernel panic by this way then use
pci=noacpi.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1690085]

2018-08-12 Thread phillips

This bug should be closed as "FIXED" in my humble opinion. "NEW" is
grossly inaccurate.

My workstation uptime is now 109 days, continuous operation without
suspend, mainly idle, mixed with episodes of heavy load on all cores and
everything in between. The technical term for this is "spectacularly
stable". Credit belongs to all involved, including AMD, kernel devs,
motherboard maker, Debian maintainers, and many other groups who made
this possible. Again in my humble opinion, the only issue remaining is
AMD's failure to explain what went wrong and exactly how they worked
around it. That is a separate bug, this one is done.

I suspect that Windows users did get this bug, but they didn't notice it
because, well use your imagination. Then it was quietly fixed in a
Windows update supplied by AMD that went out around the same time as the
Typical Power bios updates.

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-08-12 Thread Richard Baka

you (bountou), this is exactly the same problem what I have. Maybe there is a 
little difference but not much. We will be able to fix it with a little work. 
So this is an ACPI problem. ACPI(Advanced Configuration and Power Interface) is 
a hardware interface what is afforded by the manufacturer for the Operating 
System to use the notebook's power management features correctly.
There are tables in the ROM memory of your notebook that contain a lot of 
information for this. For some reason these are broken in Linux. This is what 
you see on the attached kernel output screenshot.
This is not a perfect situation.

Things you can do:
a)Install Windows. Generally the tables can be understood correctly by Windows. 
If not then the manufacturer provides drivers which fix them.
b)Disable ACPI: in this case the OS try to guess the correct behavior but it 
will never be perfect. This is why noacpi is not the correct solution. 
(temperature anomalies will occur)
c)Do manual address (Correct solution Lite version) to IOMMU and SMBUS 
controller. This can be done by the kernel parameters what I wrote: 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 for example. This is good for my 
notebook type but the values can be different by notebook subtypes.
I need the lspci -vv output after you had enabled IOMMU to give you the correct 
addresses. I can see your SMBUS is on 00:14.0 but I don't find the IOMMU which 
is necessary. This is a half-correct way.
-The best solution: recompile the DSDT/SSDT tables. This is the hardcore 
version because you should dump, decompile fix and recompile the proper tables. 
This is not easy but this can offer a similar energy management what you can 
experience on WIN 10.

So first thing to do:
Enable IOMMU, start the kernel with noacpi and copy the lspci -vv output for 
me. IOMMU should be shown there.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out

2018-08-12 Thread Moses Moore

> what output do you get when launching totem from a terminal

moses@jolyne:~/Videos$ totem vapourwave.mp4

(totem:27938): Gtk-WARNING **: 15:09:23.719: Calling
org.xfce.Session.Manager.Inhibit failed:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Inhibit"
with signature "susu" on interface "org.xfce.Session.Manager" doesn't
exist

... nothing else while the video is playing.  After quitting totem I see
this:

(totem:27938): GLib-GObject-WARNING **: 15:10:38.356: invalid (NULL)
pointer instance

(totem:27938): GLib-GObject-CRITICAL **: 15:10:38.356:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed

(totem:27938): GLib-GObject-WARNING **: 15:10:38.356: invalid (NULL)
pointer instance

(totem:27938): GLib-GObject-CRITICAL **: 15:10:38.356:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed

(totem:27938): GLib-GObject-WARNING **: 15:10:38.356: invalid (NULL)
pointer instance

(totem:27938): GLib-GObject-CRITICAL **: 15:10:38.356:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed

(totem:27938): Totem-CRITICAL **: 15:10:38.356:
totem_object_empty_menu_section: assertion 'TOTEM_IS_OBJECT (totem)'
failed


> the builtin compositor can be disabled via xfwm4-tweaks-settings...

launched xfwm4-tweaks-settings, to Compositor tab, unchecked the box [ ]
Enable display compositing.  Tried totem again, and no washed-out
transparency.  Workaround confirmed.

Why this happens with totem and not mplayer, vlc, parole, mpv, or
OpenShot, that's a head-scratcher.  Especially mpv, since mpv & totem
are linked to almost all the same libraries (mpv also uses libz.so.1 and
linux-vdso.so.1)

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

Title:
  Nvidia+XFCE: Totem window is see-through during playback, colours
  washed out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xfce4 package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+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 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out

2018-08-12 Thread Moses Moore

Forgot to mention: after turning off display compositing in xfwm4
-tweaks-settings, and running parole, the output to stderr is exactly
the same as when display compositing was turned on.

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

Title:
  Nvidia+XFCE: Totem window is see-through during playback, colours
  washed out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xfce4 package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+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 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out

2018-08-12 Thread Theo Linkspfeifer

What output do you get when opening the Totem player from a terminal
window?

The builtin compositor can be disabled via xfwm4-tweaks-settings, and
that will most likely prevent the issue from occurring. Other than that,
I suggest to test with a different window manager (e.g. "marco
--replace", afterwards "xfwm4 --replace").

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

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

Title:
  Nvidia+XFCE: Totem window is see-through during playback, colours
  washed out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xfce4 package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

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

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

Re: [Kernel-packages] [Bug 1543418] Re: Closing lid causes system hang

2018-08-12 Thread ritwik

Macbook pro 2012 model

On Sun, Aug 12, 2018, 11:09 PM Theo Linkspfeifer <1543...@bugs.launchpad.net>
wrote:

> Which hardware is that exactly?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1543418
>
> Title:
>   Closing lid causes system hang
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions
>

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

Title:
  Closing lid causes system hang

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have been having this problem for a past few weeks. I have been using this 
system for almost 1 year. I use with the power setting to suspend my system 
when I close the lid. In the past few weeks sometimes when I close the lid, the 
system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid 
screen will be back and nothing can bring the system back. I have to restart 
the system by pressing the power key. No key is working during this state. I 
tried pressing num lock and no response. It happened rarely before. But for 
past few days, my system has been getting stuck like this more. Before this, I 
used to have system crash suddenly and lose all data without any reasons. I am 
fairly new to ubuntu I don't know how to diagnose these things. Please help me.
  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+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 1543418] Re: Closing lid causes system hang

2018-08-12 Thread Theo Linkspfeifer

Which hardware is that exactly?

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

Title:
  Closing lid causes system hang

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have been having this problem for a past few weeks. I have been using this 
system for almost 1 year. I use with the power setting to suspend my system 
when I close the lid. In the past few weeks sometimes when I close the lid, the 
system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid 
screen will be back and nothing can bring the system back. I have to restart 
the system by pressing the power key. No key is working during this state. I 
tried pressing num lock and no response. It happened rarely before. But for 
past few days, my system has been getting stuck like this more. Before this, I 
used to have system crash suddenly and lose all data without any reasons. I am 
fairly new to ubuntu I don't know how to diagnose these things. Please help me.
  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+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 1778265] Re: Bionic update: upstream stable patchset 2018-06-22

2018-08-12 Thread Tim Ritberg

MODULE_SOFTDEP for crc32c is not working for me.

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

Title:
  Bionic update: upstream stable patchset 2018-06-22

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2018-06-22 (ported from v4.14.39 and v4.16.7)
     from git://git.kernel.org/

  drm/amd/display: Disallow enabling CRTC without primary plane with FB
  drm/amd/display: Fix deadlock when flushing irq
  drm/i915/audio: set minimum CD clock to twice the BCLK
  drm/i915/fbdev: Enable late fbdev initial configuration
  drm/edid: Reset more of the display info
  module: Fix display of wrong module .text address
  PCI / PM: Do not clear state_saved in pci_pm_freeze() when smart suspend is 
set
  ASoC: dmic: Fix clock parenting
  block: do not use interruptible wait anywhere
  serial: mvebu-uart: Fix local flags handling on termios update
  powerpc/eeh: Fix race with driver un/bind
  arm/arm64: KVM: Add PSCI version selection API
  tick/sched: Do not mess with an enqueued hrtimer
  x86/microcode: Do not exit early from __reload_late()
  x86/microcode/intel: Save microcode patch unconditionally
  x86/smpboot: Don't use mwait_play_dead() on AMD systems
  x86/ipc: Fix x32 version of shmid64_ds and msqid64_ds
  tools/lib/subcmd/pager.c: do not alias select() params
  objtool, perf: Fix GCC 8 -Wrestrict error
  drm/i915: Enable display WA#1183 from its correct spot
  drm/amdgpu: set COMPUTE_PGM_RSRC1 for SGPR/VGPR clearing shaders
  earlycon: Use a pointer table to fix __earlycon_table stride
  fpga-manager: altera-ps-spi: preserve nCONFIG state
  libceph: validate con->state at the top of try_write()
  libceph: reschedule a tick in finish_hunting()
  libceph: un-backoff on tick when we have a authenticated session
  ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
  crypto: drbg - set freed buffers to NULL
  KVM: arm/arm64: Close VMID generation race
  ARM: socfpga_defconfig: Remove QSPI Sector 4K size force
  ARM: amba: Don't read past the end of sysfs "driver_override" buffer
  ARM: amba: Fix race condition with driver_override
  ARM: amba: Make driver_override output consistent with other buses
  PCI: aardvark: Fix PCIe Max Read Request Size setting
  PCI: aardvark: Use ISR1 instead of ISR0 interrupt in legacy irq mode
  PCI: aardvark: Set PIO_ADDR_LS correctly in advk_pcie_rd_conf()
  PCI: aardvark: Fix logic in advk_pcie_{rd,wr}_conf()
  ANDROID: binder: prevent transactions into own process.
  vfio: ccw: process ssch with interrupts disabled
  bfq-iosched: ensure to clear bic/bfqq pointers when preparing request
  scsi: sd: Defer spinning up drive while SANITIZE is in progress
  kobject: don't use WARN for registration failures
  mtd: rawnand: tango: Fix struct clk memory leak
  mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
  mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
  mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
  mtd: spi-nor: cadence-quadspi: Fix page fault kernel panic
  ALSA: hda/realtek - change the location for one of two front mics
  ALSA: hda/realtek - Update ALC255 depop optimize
  ALSA: hda/realtek - Add some fixes for ALC233
  ALSA: hda: Hardening for potential Spectre v1
  ALSA: seq: oss: Hardening for potential Spectre v1
  ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
  ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
  ALSA: pcm: Return negative delays from SNDRV_PCM_IOCTL_DELAY.
  ALSA: control: Hardening for potential Spectre v1
  ALSA: rme9652: Hardening for potential Spectre v1
  ALSA: hdspm: Hardening for potential Spectre v1
  ALSA: asihpi: Hardening for potential Spectre v1
  ALSA: opl3: Hardening for potential Spectre v1
  ALSA: hda - Skip jack and others for non-existing PCM streams
  ALSA: dice: fix error path to destroy initialized stream data
  ALSA: dice: fix OUI for TC group
  tty: Use __GFP_NOFAIL for tty_ldisc_get()
  tty: Avoid possible error pointer dereference at tty_ldisc_restore().
  tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
  tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
  tty: Don't call panic() at tty_ldisc_init()
  drm/virtio: fix vq wait_event condition
  virtio_console: reset on out of memory
  virtio_console: move removal code

[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04

2018-08-12 Thread Marin Purgar

Also not working for my other external HDDs:

root@desktop:~# sdparm -i /dev/sdd
/dev/sdd: WDMy Book 1140  1019
Device identification VPD page:
  Addressed logical unit:
designator type: T10 vendor identification,  code set: ASCII
  vendor id: WD  
  vendor specific: My Book 1140PL1331LAGEKTJH  
root@desktop:~# sdparm -i /dev/sdf
/dev/sdf: WDMy Passport 25E2  4004
Device identification VPD page:
  Addressed logical unit:
designator type: T10 vendor identification,  code set: ASCII
  vendor id: WD  
  vendor specific: My Passport 25E2WX21D76F7R14
root@desktop:~# hdparm -y /dev/sdd

/dev/sdd:
 issuing standby command
SG_IO: bad/missing sense data, sb[]:  70 00 01 00 00 00 00 0a 00 00 00 00 00 1d 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
root@desktop:~# hdparm -y /dev/sdf

/dev/sdf:
 issuing standby command
SG_IO: bad/missing sense data, sb[]:  f0 00 01 00 50 40 00 0a 80 00 00 00 00 1d 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

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

Title:
  gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently
  working Seagate Backup+ Hub drive after upgrade to 18.04

Status in gsmartcontrol package in Ubuntu:
  Confirmed
Status in hdparm package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed
  that my Seagate Backup+ Hub external drive was displaying a series of
  puzzling symptoms:

  1. gsmartcontrol can't get SMART data from the drive. I am pretty sure
  it used to report SMART data? Here's a log of it not working:

[hz] Warning: exit: Command line did not parse.
[app] execute_smartctl(): Smartctl binary did not execute cleanly.
[app] StorageDevice::execute_device_smartctl(): Smartctl binary did 
not execute cleanly.
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Physical block size"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Logical Unit id"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Temperature Warning"
[app] SmartctlParser::parse_section_data(): Unknown Data subsection 
encountered.
[hz] Warning: exit: Some SMART command to the disk failed, or there 
was a checksum error in a SMART data structure
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Physical block size"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Logical Unit id"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Temperature Warning"
[app] SmartctlParser::parse_section_data(): Unknown Data subsection 
encountered.

  2. hdparm used to be able to spin down the drive. I had it configured
  to spin it down after a few minutes of inactivity, in the hdparm
  config file. Now that no longer happens, and hdparm can't seem to talk
  to the drive meaningfully at all:

  [anovak@octagon ~]$ sudo hdparm -I /dev/sdb

  /dev/sdb:
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 24 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  ATA device, with non-removable media
  Standards:
Likely used: 1
  Configuration:
Logical max current
cylinders   0   0
heads   0   0
sectors/track   0   0
--
Logical/Physical Sector size:   512 bytes
device size with M = 1024*1024:   0 MBytes
device size with M = 1000*1000:   0 MBytes 
cache/buffer size  = unknown
  Capabilities:
IORDY not likely
Cannot perform double-word IO
R/W multiple sector transfer: not supported
DMA: not supported
PIO: pio0 
  [anovak@octagon ~]$ sudo hdparm -y /dev/sdb

  /dev/sdb:
   issuing standby command
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 24 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  I think this may be related to https://askubuntu.com/questions/1037997
  /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone
  else having the same problem.

  3. The ZFS tools think the drive is hosed:

  [anovak@octagon ~]$ sudo zpool status hub
pool: hub
   state: UNAVAIL
  status: One or more devices could not be used because the label is missing 
or invalid.  There are insufficient replicas for the pool to continue
functioning.
  action: Destroy and re-create the pool from
a backup source.
 see: http://zfsonlinux.org/msg/ZFS-8000-5E
scan: none requested
  config:

NAME   STATE READ WRITE CKSUM
hubUNAVAIL  0 0 0  
insufficient

[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04

2018-08-12 Thread Marin Purgar

Same here:

root@desktop:~# sdparm -i /dev/sdb
/dev/sdb: Seagate   Backup+ Hub BKD781
Device identification VPD page:
  Addressed logical unit:
designator type: NAA,  code set: Binary
  0x5001
root@desktop:~# hdparm -y /dev/sdb

/dev/sdb:
 issuing standby command
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 24 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

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

Title:
  gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently
  working Seagate Backup+ Hub drive after upgrade to 18.04

Status in gsmartcontrol package in Ubuntu:
  Confirmed
Status in hdparm package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed
  that my Seagate Backup+ Hub external drive was displaying a series of
  puzzling symptoms:

  1. gsmartcontrol can't get SMART data from the drive. I am pretty sure
  it used to report SMART data? Here's a log of it not working:

[hz] Warning: exit: Command line did not parse.
[app] execute_smartctl(): Smartctl binary did not execute cleanly.
[app] StorageDevice::execute_device_smartctl(): Smartctl binary did 
not execute cleanly.
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Physical block size"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Logical Unit id"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Temperature Warning"
[app] SmartctlParser::parse_section_data(): Unknown Data subsection 
encountered.
[hz] Warning: exit: Some SMART command to the disk failed, or there 
was a checksum error in a SMART data structure
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Physical block size"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Logical Unit id"
[app] SmartctlParser::parse_section_info_property(): Unknown property 
"Temperature Warning"
[app] SmartctlParser::parse_section_data(): Unknown Data subsection 
encountered.

  2. hdparm used to be able to spin down the drive. I had it configured
  to spin it down after a few minutes of inactivity, in the hdparm
  config file. Now that no longer happens, and hdparm can't seem to talk
  to the drive meaningfully at all:

  [anovak@octagon ~]$ sudo hdparm -I /dev/sdb

  /dev/sdb:
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 24 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  ATA device, with non-removable media
  Standards:
Likely used: 1
  Configuration:
Logical max current
cylinders   0   0
heads   0   0
sectors/track   0   0
--
Logical/Physical Sector size:   512 bytes
device size with M = 1024*1024:   0 MBytes
device size with M = 1000*1000:   0 MBytes 
cache/buffer size  = unknown
  Capabilities:
IORDY not likely
Cannot perform double-word IO
R/W multiple sector transfer: not supported
DMA: not supported
PIO: pio0 
  [anovak@octagon ~]$ sudo hdparm -y /dev/sdb

  /dev/sdb:
   issuing standby command
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 24 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  I think this may be related to https://askubuntu.com/questions/1037997
  /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone
  else having the same problem.

  3. The ZFS tools think the drive is hosed:

  [anovak@octagon ~]$ sudo zpool status hub
pool: hub
   state: UNAVAIL
  status: One or more devices could not be used because the label is missing 
or invalid.  There are insufficient replicas for the pool to continue
functioning.
  action: Destroy and re-create the pool from
a backup source.
 see: http://zfsonlinux.org/msg/ZFS-8000-5E
scan: none requested
  config:

NAME   STATE READ WRITE CKSUM
hubUNAVAIL  0 0 0  
insufficient replicas
  ata-ST6000DM003-2CY186_ZF200PC8  UNAVAIL  0 0 0

  This may be related to the drive having adopted a new /dev/disk/by-id
  name during the upgrade? I think it was "ata-
  ST6000DM003-2CY186_ZF200PC8" when I added it to my zpool by its
  symlink under /dev/disks/by-id, but now it is "usb-
  Seagate_Backup+_Hub_BK_NA8TQC87-0:0":

  [anovak@octagon ~]$ ls -lah 
/dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0\:0
  lrwxrwxrwx 1 root root 9 May 31 20:52 
/dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0:0 -> ../../sdb

  This *shouldn't* cause trouble; you should be

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

2018-08-12 Thread Brad

@Boris, it depends what is the touchpad device you have in your Lapbook Air.
There is a couple of patches rolled into kernel 4.17 and 4.18 ...

https://forum.manjaro.org/t/lenovo-ideapad-330-touchpad-not-working/50764/12
https://forum.manjaro.org/t/touchpad-syna3602-0911-5288-not-working-at-all/36269/49

plus the above mentioned SYNA3602 patch for the Ubuntu distro.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

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

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

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

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

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

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

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

2018-08-12 Thread whl2

For the record - dropped all 3d-party fan-controlling software, issue still 
present with mainline kernel 4.16.18 and nvidia driver 396.51.
Wasn't lucky enough to boot 4.18-rc

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  Things tried:

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

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

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

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

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Re: [Kernel-packages] [Bug 1543418] Re: Closing lid causes system hang

2018-08-12 Thread ritwik

Recently I moved to ubuntu 18.04. Still the issue is happening
occasionally. Sometimes the whole system restarts.

Another issue with 18.05 noticed. In auto brightness the screen is turning
off sometimes when I am using it at minimal brightness. I think this should
be easily fixable.

On Sun, Aug 12, 2018, 7:54 PM Theo Linkspfeifer <1543...@bugs.launchpad.net>
wrote:

> Is this problem still present in current Ubuntu releases?
>
> ** Package changed: xubuntu-default-settings (Ubuntu) => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1543418
>
> Title:
>   Closing lid causes system hang
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+subscriptions
>

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

Title:
  Closing lid causes system hang

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have been having this problem for a past few weeks. I have been using this 
system for almost 1 year. I use with the power setting to suspend my system 
when I close the lid. In the past few weeks sometimes when I close the lid, the 
system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid 
screen will be back and nothing can bring the system back. I have to restart 
the system by pressing the power key. No key is working during this state. I 
tried pressing num lock and no response. It happened rarely before. But for 
past few days, my system has been getting stuck like this more. Before this, I 
used to have system crash suddenly and lose all data without any reasons. I am 
fairly new to ubuntu I don't know how to diagnose these things. Please help me.
  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+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 1543418] Re: Closing lid causes system hang

2018-08-12 Thread Theo Linkspfeifer

Is this problem still present in current Ubuntu releases?

** Package changed: xubuntu-default-settings (Ubuntu) => linux (Ubuntu)

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

Title:
  Closing lid causes system hang

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have been having this problem for a past few weeks. I have been using this 
system for almost 1 year. I use with the power setting to suspend my system 
when I close the lid. In the past few weeks sometimes when I close the lid, the 
system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid 
screen will be back and nothing can bring the system back. I have to restart 
the system by pressing the power key. No key is working during this state. I 
tried pressing num lock and no response. It happened rarely before. But for 
past few days, my system has been getting stuck like this more. Before this, I 
used to have system crash suddenly and lose all data without any reasons. I am 
fairly new to ubuntu I don't know how to diagnose these things. Please help me.
  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543418/+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 1543418] [NEW] Closing lid causes system hang

You have been subscribed to a public bug:

I have been having this problem for a past few weeks. I have been using this 
system for almost 1 year. I use with the power setting to suspend my system 
when I close the lid. In the past few weeks sometimes when I close the lid, the 
system doesn't gets suspended. Instead, it gets stuck. When i reopen the lid 
screen will be back and nothing can bring the system back. I have to restart 
the system by pressing the power key. No key is working during this state. I 
tried pressing num lock and no response. It happened rarely before. But for 
past few days, my system has been getting stuck like this more. Before this, I 
used to have system crash suddenly and lose all data without any reasons. I am 
fairly new to ubuntu I don't know how to diagnose these things. Please help me.
Thank you

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

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

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

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

2018-08-12 Thread Boris Urman

Hi, does anyone know when this bug will be fixed?

I really would love to use Ubuntu on my Chuwi Lapbook Air but I can't
because touchpad doesn't work.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

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

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

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

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

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

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

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

2018-08-12 Thread pHeLiOn

@yeboster - it's possible that you might not need the patched kernel to
get suspend to work. Please see here for troubleshooting and to discuss
further: https://ubuntuforums.org/showthread.php?t=2395562

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

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

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  Systems with acpi-lpss can't do S3/S4 on Bionic.

  [Test]
  Users confirmed these patches work for them.

  [Fix]
  Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system
  sleep handling) applies quirks for both runtime and system suspend.
  This causes problems for some systems, so avoid using quirks on S3 and
  S4.

  [Regression Potential]
  Low. These patches are in upstream stable, and it brings back driver's
  old behavior.

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

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

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

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

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

  Correct behaviour is -

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

  What happens -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

And this is with IOMMU enabled (and without the pci=noacpi) : 
http://prntscr.com/khn3jw
I can still start with IOMMU enabled if I add "pci=noacpi".

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1786676] Status changed to Confirmed

2018-08-12 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  package linux-modules-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: Extrahierte Daten für
  »./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« können nicht
  nach »/lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko.dpkg-new«
  kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installation does not work (in vmware virtual machine

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_41
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   linux-modules-4.15.0-24-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1149 F pulseaudio
richterj   1766 F pulseaudio
  Date: Mon Jul 30 13:39:45 2018
  Dependencies:
   
  ErrorMessage: Extrahierte Daten für 
»./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« können nicht nach 
»/lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
  InstallationDate: Installed on 2018-05-04 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d5f04d13-e0b9-4058-a2ca-8518193fbc27 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-modules-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: Extrahierte Daten für 
»./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« können nicht nach 
»/lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786676/+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 1786676] [NEW] package linux-modules-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« kön

2018-08-12 Thread Joerg Richter

Public bug reported:

Installation does not work (in vmware virtual machine

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-modules-4.15.0-24-generic 4.15.0-24.26
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_41
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 linux-modules-4.15.0-24-generic:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1149 F pulseaudio
  richterj   1766 F pulseaudio
Date: Mon Jul 30 13:39:45 2018
Dependencies:
 
ErrorMessage: Extrahierte Daten für 
»./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« können nicht nach 
»/lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
InstallationDate: Installed on 2018-05-04 (99 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 ens33 no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d5f04d13-e0b9-4058-a2ca-8518193fbc27 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2
RfKill:
 
SourcePackage: linux
Title: package linux-modules-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: Extrahierte Daten für 
»./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« können nicht nach 
»/lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-modules-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: Extrahierte Daten für
  »./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« können nicht
  nach »/lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko.dpkg-new«
  kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms

Status in linux package in Ubuntu:
  New

Bug description:
  Installation does not work (in vmware virtual machine

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_41
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   linux-modules-4.15.0-24-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1149 F pulseaudio
richterj   1766 F pulseaudio
  Date: Mon Jul 30 13:39:45 2018
  Dependencies:
   
  ErrorMessage: Extrahierte Daten für 
»./lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko« können nicht nach 
»/lib/modules/4.15.0-24-generic/kernel/fs/aufs/aufs.ko.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
  InstallationDate: Installed on 2018-05-04 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID

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

2018-08-12 Thread axt

I mean Win 1803 of course, "1804" doesn't exist.

--
You 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 possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

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

Thank you!!

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

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

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

2018-08-12 Thread axt

I mean Win 1803 of course.

--
You 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

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:

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:

---

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 possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

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

Thank you!!

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

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

2018-08-12 Thread axt

#592, #602
@Robert R (roremich)

17.10 w/o .1 is *toxic* (and anyway EoS, with .1 also). Already the
first boot up changes the value. The UEFI is destroyed, so to speak.
Btw., that would not have happened in CSM mode instead UEFI mode.

Hard cheese, inform in advance.

Installing a clean kernel in a live system has no effect because it
doesn't allow you to boot.

You could try this:

1. Remove the HDD and connect temporary exclusive at another System!
2. Install Ubuntu 18.04.1 64 bit in UEFI mode!
3. Insert this HDD in the Lenovo G50-80 and try to boot! This should correct
the false value.

As a thinkable alternative:

1. Remove the HDD and connect temporary exclusive at another System!
2. Install Win10 1804 64 bit in UEFI mode!
(https://www.microsoft.com/en-us/software-download/windows10ISO - during the
installation routine try "I don't have a product key"/"Ich habe keinen
Produktschlüssel"!)
3. Copy the flashing tool with the current UEFI version to the harddisk
(https://pcsupport.lenovo.com/de/en/products/LAPTOPS-AND-NETBOOKS/LENOVO-G-SERIES-LAPTOPS/G50-80/downloads/DS102231
- sadly old A0)!
3. Insert this HDD in the Lenovo G50-80 and try to boot!
4. Flash the current UEFI!
5. With a little bit luck the UEFI values will be set to defaults.
6. Now you could kill Windows with an Ubuntu 18.04.1 64 bit installation.

One more comment: Asking at https://forum.ubuntuusers.de/topic
/corrupted-bios-due-to-intel-spi-bug-in-kernel-/ isn't the best idea.

And finally: Nail the 17.10-DVD to the wall!

--
You 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

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:

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:

---

Affected serial flash devices by manufacturer part number, JEDEC ID

[Kernel-packages] [Bug 1786669] [NEW] Xorg freeze / nvidia-driver-390 does not boot

2018-08-12 Thread igi

Public bug reported:

Ubuntu installed in legacy mode (efi not supported)
graphic card: Nvidia GF108 [GeForce GT 520]
Kernel: linux-image-4.15.0-30-generic

With default driver active [xserver-xorg-video-nouveau] the performance
is reduced (compared to active nvidia driver in previous 16.04
installation). Running games often leads to screen freeze (hard reboot
necessary).

On the other hand proprietary drivers do not work properly:
1) with nvidia-driver-390 the system locks before showing gdm login (bad chars 
shown) with last kernel;
2) with nvidia-driver-390 the screen is forced to 680x480 res using kernel 
linux-image-4.15.0-23-generic; also LAN/internet does not work;
3) with nvidia-340 the monitor switches off during boot and the boot does not 
continue;

Also tried to activate the nvidia ppa (ppa:graphics-drivers/ppa) to try
the legacy driver (304), but I can't since it breaks several other
packages.

Googling around my guess either is for bugs in kernels from 4.15.0-23 or
for signed modules not working without efi.

Thanks for your support!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompizPlugins: 
[core,composite,opengl,decor,regex,compiztoolbox,move,resize,imgpng,place,animation,expo,grid,vpswitch,mousepoll,workarounds,snap,gnomecompat,unitymtgrabhandles,session,ezoom,wall,fade,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 12 09:34:04 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since before I upgraded
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
InstallationDate: Installed on 2018-08-08 (3 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=6a0b9e44-0c07-4365-bdbb-a6a9ac7f88bd ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1105
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F1A55-M
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd08/31/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


** Tags: amd64 apport-bug bionic freeze ubuntu

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Xorg freeze / nvidia-driver-390 does not boot

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu installed in legacy mode (efi not supported)
  graphic card: Nvidia GF108 [GeForce GT 520]
  Kernel: linux-image-4.15.0-30-generic

  With default driver active [xserver-xorg-video-nouveau] the
  performance is reduced (compared to active nvidia driver in previous
  16.04 installation). Running games often leads to screen freeze (hard
  reboot necessary).

  On the other hand proprietary drivers do not work properly:
  1) with nvidia-driver-390 the system locks before showing gdm login (bad

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

2018-08-12 Thread Ruben

Thanks, solved my problem in bios uefi Lenovo G50-80.

--
You 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

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:

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:

---

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 possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

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

Thank you!!

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

[Kernel-packages] [Bug 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3

Is it possible that the idle power state of the driver is broken?
Referring to this output in the dmesg:
...
[  753.636901] mwifiex_pcie :01:00.0: Firmware wakeup failed
...

** Description changed:

  I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
- After an varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
+ After a varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
  My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.
  
  Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
  lsb_release:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  logs as attachments are following

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

Title:
  wifi (mwifiex_pcie) stops working undeterministically in 18.04 on
  Surface Pro 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
  After a varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
  My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.

  Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
  lsb_release:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  logs as attachments are following

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

2018-08-12 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

** Tags added: bionic

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

Title:
  wifi (mwifiex_pcie) stops working undeterministically in 18.04 on
  Surface Pro 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
  After a varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
  My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.

  Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
  lsb_release:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  logs as attachments are following

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+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 1786664] [NEW] wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3

Public bug reported:

I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
After a varying amount of time the wifi connection is gone. The driver does not 
seem to respond anymore to any action invoked by the gnome ui.
My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.

Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
lsb_release:
Description:Ubuntu 18.04.1 LTS
Release:18.04

logs as attachments are following

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


** Tags: bionic

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

Title:
  wifi (mwifiex_pcie) stops working undeterministically in 18.04 on
  Surface Pro 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
  After a varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
  My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.

  Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
  lsb_release:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  logs as attachments are following

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+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 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3

** Attachment added: "mwifiex.lspci.crop.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+attachment/5174353/+files/mwifiex.lspci.crop.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/1786664

Title:
  wifi (mwifiex_pcie) stops working undeterministically in 18.04 on
  Surface Pro 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
  After a varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
  My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.

  Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
  lsb_release:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  logs as attachments are following

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+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 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3

** Attachment added: "networkmanager0804.crop.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+attachment/5174355/+files/networkmanager0804.crop.log

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

Title:
  wifi (mwifiex_pcie) stops working undeterministically in 18.04 on
  Surface Pro 3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using the mainline kernel on Ubuntu 18.04 on a Surface Pro 3.
  After a varying amount of time the wifi connection is gone. The driver does 
not seem to respond anymore to any action invoked by the gnome ui.
  My only known workaround for this is to reboot. In this state the shutdown 
process may take several minutes.

  Version signature: Ubuntu 4.15.0-30.32-generic 4.15.18
  lsb_release:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  logs as attachments are following

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786664/+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 1786664] Re: wifi (mwifiex_pcie) stops working undeterministically in 18.04 on Surface Pro 3