[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2018-02-09 Thread Kai-Heng Feng
Can you manually install libssl1.1? Or skip installing header files, if
you don't use any DKMS.

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  A user reported his NVMe went out to lunch after S3.

  [Fix]
  Disable APST for this particular NVMe + Motherboard setup.

  [Test]
  User confirmed this quirk works for his system.

  [Regression Potential]
  Very Low. This applies to a specific device setup, also user can
  override this quirk by "nvme_core.force_apst=1".

  === Original Bug Report ===
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
    rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
    rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
    rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
    rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
    rwt:4 rwl:4 idle_power:- active_power:-
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon runnin

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2018-02-09 Thread Ricardus
This bug affected me on my old Dell Mini 9. I hadn't used the thing in
years because the battery died. I found am inexpensive battery and
figured I'd make a coffee table machine putting lubuntu on it, and I had
the same problem. A friend of mine and I fixed it as per this thread:

https://ubuntuforums.org/showthread.php?t=2384579&p=13738255#post13738255

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1724639/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2018-02-09 Thread Kai-Heng Feng
Looks like there's a patch but not upstreamed yet,
https://patchwork.freedesktop.org/patch/157327/

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=194521
   Importance: Unknown
   Status: Unknown

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

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

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1747463/+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 1730480] Re: Problem after 17.04 to 17.10 upgrade

2018-02-09 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Problem after 17.04 to 17.10 upgrade

Status in linux package in Ubuntu:
  Expired

Bug description:
  Problem after 17.04 to 17.10 upgrade - seven days ago.
  I have to boot using Grub, in recovery mode. System works ok. During power 
down, I get -
  A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 
30 - and then proceeds to finish.
  System is an AMD64, with graphics on the motherboard. I will search for more 
detail if necessary.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gherrick   1646 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852
  InstallationDate: Installed on 2016-05-05 (551 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-MA74GMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA74GMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1736816] Re: system freezed

2018-02-09 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  system freezed

Status in linux package in Ubuntu:
  Expired

Bug description:
  laptop freezed with no response at all. no keyboard keys were working
  . this suddenly happened when i just typing into the word processor.

  my laptop has 6gb RAM and 1TB HDD

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nilanjan   1424 F pulseaudio
   /dev/snd/controlC0:  nilanjan   1424 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  7 04:02:06 2017
  InstallationDate: Installed on 2017-12-04 (2 days ago)
  InstallationMedia: It
  MachineType: Dell Inc. Inspiron 3537
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=59520f57-087f-4c11-8c5c-580195d38855 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0N7YKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn0N7YKW:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.family: 00
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736816/+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 1737291] Re: Lenovo y7070

2018-02-09 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Lenovo y7070

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi same problem here lenovo y7070...biod cant save no usb no uefi no
  lagacy...after ubuntu 1710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737291/+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 1737321] Re: touchpad does not work anymore

2018-02-09 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  touchpad does not work anymore

Status in linux package in Ubuntu:
  Expired

Bug description:
  i have a Toshiba Satellite

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-103-generic 4.4.0-103.126
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wim3982 F pulseaudio
   /dev/snd/controlC1:  wim3982 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Dec  9 14:27:38 2017
  HibernationDevice: RESUME=UUID=2baeb6cd-acc1-448f-a9b0-b9d879630ea6
  InstallationDate: Installed on 2017-04-04 (248 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA SATELLITE L870-141
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=3118702c-2f38-48ea-ab5d-2eadedbb2e6e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEL870-141:pvrPSKBLE-022004DU:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE L870-141
  dmi.product.version: PSKBLE-022004DU
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737321/+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 1737522] Re: cfq scheduler can write parts of sequential write in reverse order

2018-02-09 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  cfq scheduler can write parts of sequential write in reverse order

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm opening a raw disk device (like /dev/sdb) with O_DIRECT and then
  doing write() calls. The device is actually USB mass storage. Looking
  at the USB packets with Wireshark, I see that the write() calls are
  being split into multiple SCSI writes. That part is okay I guess. The
  problem is that these writes can happen in reverse order. Suppose the
  write() call is writing to sectors 100 to 200. The first SCSI write
  may write 150 to 200 and the second SCSI write may write 100 to 149.

  Correctness does appear to be maintained. I only had a problem with
  correctness because I'm abusing the protocol for writing to a hacked
  digital photo frame via
  https://github.com/dreamlayers/st220x/blob/master/libst2205/st2205.c .
  The photo frame doesn't fully process the protocol and only looks at
  the data as a series of USB packets.

  However, this is bad for performance with hard disks. Surely if you
  have a sequential write, the optimal way to do that write is
  sequentially from start to finish. Since changing the scheduler for
  that block device from cfq to noop fixes this problem, I assume it has
  to do with the elevator algorithm use to optimize hard disk access.
  But surely such optimization only makes sense between contiguous
  sequential writes, and not for splitting up one such write.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-19-generic 4.13.0-19.22
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-19-generic.
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   2116 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfa20 irq 30'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,1458a002,00100101'
 Controls  : 63
 Simple ctrls  : 26
  CurrentDesktop: XFCE
  Date: Mon Dec 11 05:23:12 2017
  HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3R
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=52543c1b-1764-4766-a504-f4b94422fa6e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-30 (71 days ago)
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737522/+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 1748486] Re: linux-aws: -proposed tracker

2018-02-09 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748484
+ kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748484
- kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748484
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748486/+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 1748489] Re: linux-aws: -proposed tracker

2018-02-09 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748484
+ kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748484
- kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1748484
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748489/+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 1748484] Re: linux: 4.4.0-114.137 -proposed tracker

2018-02-09 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1748486 (linux-aws), bug 1748488 (linux-lts-xenial)
  derivatives: bug 1748489 (linux-aws), bug 1748490 (linux-euclid), bug 1748491 
(linux-gke), bug 1748492 (linux-kvm), bug 1748493 (linux-raspi2), bug 1748494 
(linux-snapdragon)
+ kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1748486 (linux-aws), bug 1748488 (linux-lts-xenial)
  derivatives: bug 1748489 (linux-aws), bug 1748490 (linux-euclid), bug 1748491 
(linux-gke), bug 1748492 (linux-kvm), bug 1748493 (linux-raspi2), bug 1748494 
(linux-snapdragon)
  kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.4.0-114.137 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1748486 (linux-aws), bug 1748488 (linux-lts-xenial)
  derivatives: bug 1748489 (linux-aws), bug 1748490 (linux-euclid), bug 1748491 
(linux-gke), bug 1748492 (linux-kvm), bug 1748493 (linux-raspi2), bug 1748494 
(linux-snapdragon)
  kernel-stable-phase-changed:Saturday, 10. February 2018 03:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748484/+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 1748475] Re: linux: 4.13.0-34.37 -proposed tracker

2018-02-09 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1748476 (linux-azure), bug 1748477 (linux-azure-edge), bug 
1748478 (linux-gcp), bug 1748479 (linux-hwe), bug 1748480 (linux-hwe-edge), bug 
1748481 (linux-oem)
  derivatives: bug 1748483 (linux-raspi2)
+ kernel-stable-phase-changed:Saturday, 10. February 2018 03:03 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1748476 (linux-azure), bug 1748477 (linux-azure-edge), bug 
1748478 (linux-gcp), bug 1748479 (linux-hwe), bug 1748480 (linux-hwe-edge), bug 
1748481 (linux-oem)
  derivatives: bug 1748483 (linux-raspi2)
  kernel-stable-phase-changed:Saturday, 10. February 2018 03:03 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.13.0-34.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

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

  backports: bug 1748476 (linux-azure), bug 1748477 (linux-azure-edge), bug 
1748478 (linux-gcp), bug 1748479 (linux-hwe), bug 1748480 (linux-hwe-edge), bug 
1748481 (linux-oem)
  derivatives: bug 1748483 (linux-raspi2)
  kernel-stable-phase-changed:Saturday, 10. February 2018 03:03 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748475/+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 1748513] Re: BUG: unable to handle kernel paging request at 00007f29ec101010

2018-02-09 Thread Simon Déziel
I just hit a similar looking bug/oops why another machine (a laptop this
time) also running the -proposed kernel:

BUG: unable to handle kernel NULL pointer dereference at 0009
IP: [] csum_and_copy_from_iter+0x55/0x4c0
PGD 0 
Oops:  [#1] SMP 
Modules linked in: veth xt_CHECKSUM iptable_mangle xt_comment ctr ccm ec_sys 
bridge stp llc nf_log_ipv6 ip6table_filter ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat nf_nat_ipv6 ip6_tables nf_log_ip
 ghash_clmulni_intel snd psmouse ahci soundcore r8169 mei_me cfg80211 rtsx_pci 
mii input_leds libahci mei media vhost_net vhost macvtap macvlan kvm_intel 
i2c_hid kvm intel_lpss_acpi intel_lpss irqbypass a
CPU: 1 PID: 9573 Comm: dnsmasq Tainted: PW  O4.4.0-113-generic 
#136-Ubuntu
Hardware name: System76Lemur/Lemur, BIOS 5.12 02/17/2017
task: 88078a91 ti: 88083699c000 task.ti: 88083699c000
RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
RSP: 0018:88083699fa18  EFLAGS: 00010246
RAX: b1729fd0 RBX: 001c RCX: 88083699fe98
RDX: 88083699fa94 RSI: 001c RDI: 88077a0b8824
RBP: 88083699fa80 R08:  R09: 88077a0b8824
R10: 88077a0b8824 R11: 88077a0b8800 R12: 88083699fe98
R13:  R14: 00ffb1ea6920 R15: 0001
FS:  7f8de7b35880() GS:88086ec8() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 0009 CR3: 00078af4 CR4: 00360670
Stack:
 88084e001600 b172d1d7 880776b48600 88083699faaf
 88083699fa94 01c0  09348cbfe217bf5c
 001c 880776b48600  88083699fd30
Call Trace:
 [] ? __alloc_skb+0x87/0x1f0
 [] ip_generic_getfrag+0x56/0xe0
 [] raw_getfrag+0xaf/0x100
 [] __ip_append_data.isra.45+0x98a/0xb90
 [] ? raw_recvmsg+0x1c0/0x1c0
 [] ? raw_recvmsg+0x1c0/0x1c0
 [] ip_append_data.part.46+0x7a/0xe0
 [] ip_append_data+0x34/0x40
 [] raw_sendmsg+0x724/0xc00
 [] ? aa_sk_perm+0x70/0x210
 [] ? aa_sock_msg_perm+0x61/0x150
 [] inet_sendmsg+0x6b/0xa0
 [] sock_sendmsg+0x3e/0x50
 [] SYSC_sendto+0x101/0x190
 [] ? sock_setsockopt+0x180/0x830
 [] ? apparmor_socket_setsockopt+0x22/0x30
 [] SyS_sendto+0xe/0x10
 [] entry_SYSCALL_64_fastpath+0x1c/0x93
Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
RIP  [] csum_and_copy_from_iter+0x55/0x4c0
 RSP 
CR2: 0009
---[ end trace f6995f3da4973edf ]---

I'm not sure if those 2 are related or not.

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

Title:
  BUG: unable to handle kernel paging request at 7f29ec101010

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel paging request at 7f29ec101010
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 82fcef6f9067 PUD 2fd1615e067 PMD 2fcef77e067 PTE 82fd0009f867
  Oops: 0001 [#1] SMP 
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_
   fjes wmi
  CPU: 39 PID: 27347 Comm: fping Not tainted 4.4.0-113-generic #136-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
  task: 88bd1125e200 ti: 897d0285 task.ti: 897d0285
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:897d02853a18  EFLAGS: 00010246
  RAX: 0018 RBX: 0006 RCX: 897d02853e98
  RDX: 897d02853a94 RSI: 0040 RDI: 8afcfba4ea24
  RBP: 897d02853a80 R08:  R09: 8afcfba4ea24
  R10: 8afcfba4ea24 R11: 8afcfba4ea00 R12: 897d02853e98
  R13:  R14: 1ee730fc3e9fb34c R15: 7f29ec101008
  FS:  7f29ec282700() GS:8afd7ec4() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f29ec101010 CR3: 02fce5462000 CR4: 00360670
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88bd7ec07340 9772d1d7 8afcf02d8f00 897d02853aaf
   897d02853a94 01c0  1ee730fc3e9fb34c
   0040 8afcf02d8f00  897d02853d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x

[Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2018-02-09 Thread Jakub Paś
Still a problem with Sony WH-1000xm2 headsed.


Feb 10 02:33:17 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 218182 us (= 38484 bytes) in audio stream
Feb 10 02:33:17 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 343085 us (= 60520 bytes) in audio stream
Feb 10 02:33:18 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 218071 us (= 38464 bytes) in audio stream
Feb 10 02:33:18 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 343087 us (= 60520 bytes) in audio stream
Feb 10 02:33:20 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 1718049 us (= 303060 bytes) in audio stream
Feb 10 02:33:20 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 342982 us (= 60500 bytes) in audio stream
Feb 10 02:33:20 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 282044 us (= 49752 bytes) in audio stream
Feb 10 02:33:49 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 10705 us (= 1888 bytes) in audio stream
Feb 10 02:34:11 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 31721 us (= 5592 bytes) in audio stream
Feb 10 02:34:11 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 205154 us (= 36188 bytes) in audio stream
Feb 10 02:34:11 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 37079 us (= 6540 bytes) in audio stream
Feb 10 02:34:11 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 7092 us (= 1248 bytes) in audio stream
Feb 10 02:34:11 localhost pulseaudio[3304]: [bluetooth] 
module-bluetooth-device.c: Skipping 37116 us (= 6544 bytes) in audio stream

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1598312] Re: Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz

2018-02-09 Thread WSmart
Thanks for all the work everyone put into developing this, Vladimir in
particular.   The acpi=noirq work around is working here.   I wanted to
add, along with the scaling and the reboot fail issues, I also was not
able to run ubiquity.  The installer would crash giving me
freedesktop.org errors.   I installed xfce4-power-manger to the live
environment and was able to use ubiquity and install the system from
there, booting to the 800mhz scaling limit.

Thanks all.  
With alcohol you get all the confidence and none of the competence.

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

Title:
  Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  http://askubuntu.com/questions/789096/cant-scale-frequencies-of-amd-
  turion-cpu-it-always-jumps-to-lowest

  The CPU does not scale frequency on kernel "4.2.0-41-generic
  #48~14.04.1-Ubuntu SMP Fri Jun 24 17:09:15". The notebook behaves very
  slow despite on Windows Vista it works great.

  Cpufreq-info program shows that there is a limit on the frequency setting 
between 800MHz and 800MHz. I tried to impose the frequency by setting the 
"performance policy" or by setting the limit in /etc/default/cpufrequency, but 
it does not work. 
  Next I tried to check the BIOS limits, because there are some suggestions 
that some battery/power supply problems could cause the BIOS to set the limits 
on CPU freq but it is not there.

  The CPU freq scaling works good on 'linux-image-4.1.26-040126-generic'
  kernel. It does not work on this kernel "4.2.0-41-generic" and "linux-
  headers-4.2.0-38-generic". The current workaround is to switch off the
  ACPI by "acpi=off" boot parameter. Using this setting the CPU
  frequency scaling works but it makes the system single CPU core only.

  Hardware: HP Compaq 6715B notebook with AMD Turion CPU TL-58 and
  powernow-k8 cpufreq driver. I've heard some posts that on others HP
  notebooks there are similar problems with the freq scaling.

  
  $ cpufreq-info 
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 109 us.
hardware limits: 800 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 
MHz:99,93%  (1)
  analyzing CPU 1:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 109 us.
hardware limits: 800 MHz - 1.90 GHz
available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 800 MHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 
MHz:99,93%  (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-41-generic 4.2.0-41.48~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  Uname: Linux 4.2.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jul  1 23:49:34 2016
  InstallationDate: Installed on 2016-04-08 (83 days ago)
  InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1598312/+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-02-09 Thread Lucas Zanella
I think I got it: http://pastebin.com/raw/squFVnGi

I'm counting with the idea that this 4.13.0-34 is the new one, not the
old one I had. I hope it is.

Just booted and PCIe wireless is working. uname-r gives
4.13.0-34-generic.

Going to leave the system rest for a while to see if something happens,
not going to download torrent again.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

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

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

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

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

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

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

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

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

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

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

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

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

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

2018-02-09 Thread Lucas Zanella
Nevermind I installed libssl1.1 by adding the bionic rep, however right
before I could reinstall the kernel the system entered in read-only
mode. I'm gonna try to enter and install the new kernel in some way.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

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

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

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

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

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

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

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

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

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

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

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

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

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

2018-02-09 Thread Lucas Zanella
I just installed your new kernel on the old SSD and changed the
nvme_core_..._us to 0

seems that a dependency is missing on the kernel:

oblems prevent configuration of linux-headers-4.13.0-34-generic:
 linux-headers-4.13.0-34-generic depends on libssl1.1 (>= 1.1.0); however:
  Package libssl1.1 is not installed.

dpkg: error processing package linux-headers-4.13.0-34-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-4.13.0-34-generic (4.13.0-34.37~lp1746340) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
update-initramfs: Generating /boot/initrd.img-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0+
Found initrd image: /boot/initrd.img-4.15.0+
Found linux image: /boot/vmlinuz-4.14.0-17-generic
Found initrd image: /boot/initrd.img-4.14.0-17-generic
Found linux image: /boot/vmlinuz-4.13.0-34-generic
Found initrd image: /boot/initrd.img-4.13.0-34-generic
Found linux image: /boot/vmlinuz-4.13.0-32-generic
Found initrd image: /boot/initrd.img-4.13.0-32-generic
Found linux image: /boot/vmlinuz-4.13.0-21-generic
Found initrd image: /boot/initrd.img-4.13.0-21-generic
Adding boot menu entry for EFI firmware configuration
done
Setting up linux-image-extra-4.13.0-34-generic (4.13.0-34.37~lp1746340) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
update-initramfs: Generating /boot/initrd.img-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.13.0-34-generic /boot/vmlinuz-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.13.0-34-generic 
/boot/vmlinuz-4.13.0-34-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0+
Found initrd image: /boot/initrd.img-4.15.0+
Found linux image: /boot/vmlinuz-4.14.0-17-generic
Found initrd image: /boot/initrd.img-4.14.0-17-generic
Found linux image: /boot/vmlinuz-4.13.0-34-generic
Found initrd image: /boot/initrd.img-4.13.0-34-generic
Found linux image: /boot/vmlinuz-4.13.0-32-generic
Found initrd image: /boot/initrd.img-4.13.0-32-generic
Found linux image: /boot/vmlinuz-4.13.0-21-generic
Found initrd image: /boot/initrd.img-4.13.0-21-generic
Adding boot menu entry for EFI firmware configuration
done
Errors were encountered while processing:
 linux-headers-4.13.0-34-generic

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

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

2018-02-09 Thread Lucas Zanella
You mean I need to boot with the parameter on your new kernel? I'm gonna
try it

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

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

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

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

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

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

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

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

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

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

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

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

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

[Kernel-packages] [Bug 1748567] [NEW] ethtool -p fails to light NIC LED on HiSilicon D05 systems

2018-02-09 Thread dann frazier
Public bug reported:

[Impact]
ethtool -p doesn't work for HiSilicon D05 onboard 10G NICs. From ethtool(8):

-%<---
-p --identify
   Initiates adapter-specific action  intended to enable an operator to 
easily identify
   the adapter by sight. Typically this involves blinking one or more LEDs 
on the spe‐
   cific network port.
-%<---

[Test Case]
Run "ethtool -p " for one of the impacted NIC interfaces. Watch for 
blinky light.

[Regression Risk]
Fix is local to a specific driver for onboard NICs, and a clean upstream 
cherry-pick.

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

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: dann frazier (dannf)
   Status: In Progress

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

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

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

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

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

Title:
  ethtool -p fails to light NIC LED on HiSilicon D05 systems

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

Bug description:
  [Impact]
  ethtool -p doesn't work for HiSilicon D05 onboard 10G NICs. From ethtool(8):

  -%<---
  -p --identify
 Initiates adapter-specific action  intended to enable an operator to 
easily identify
 the adapter by sight. Typically this involves blinking one or more 
LEDs on the spe‐
 cific network port.
  -%<---

  [Test Case]
  Run "ethtool -p " for one of the impacted NIC interfaces. Watch for 
blinky light.

  [Regression Risk]
  Fix is local to a specific driver for onboard NICs, and a clean upstream 
cherry-pick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748567/+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 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-09 Thread Kamal Mostafa
@Paul, I cannot provide an exact date, but it will most likely be within
the next five days.

For the record, we've decided to pull in an additional group of patches
so the next release linux-aws kernel will now be version
(4.4.0-1052.61).  I'll post here once an official build of that becomes
available for verification.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+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 1748565] [NEW] Bluetooth: hci0: last event is not cmd complete (0x0f)

2018-02-09 Thread Cristian Aravena Romero
Public bug reported:

Hello,

dmesg:
[ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-9-generic 4.15.0-9.10
ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
Uname: Linux 4.15.0-9-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   1811 F pulseaudio
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Fri Feb  9 20:35:29 2018
InstallationDate: Installed on 2017-10-13 (119 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-9-generic N/A
 linux-backports-modules-4.15.0-9-generic  N/A
 linux-firmware1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: linux
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug bionic package-from-proposed

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=198699
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1748565/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2018-02-09 Thread Steve Roberts
Unable to install the file:
linux-headers-4.13.0-34-generic_4.13.0-34.37~lp1746340_amd64.deb

due to missing dependency libssl1.1

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  A user reported his NVMe went out to lunch after S3.

  [Fix]
  Disable APST for this particular NVMe + Motherboard setup.

  [Test]
  User confirmed this quirk works for his system.

  [Regression Potential]
  Very Low. This applies to a specific device setup, also user can
  override this quirk by "nvme_core.force_apst=1".

  === Original Bug Report ===
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
    rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
    rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
    rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
    rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
    rwt:4 rwl:4 idle_power:- active_power:-
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission den

[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

2018-02-09 Thread Peter Milley
Still no response from the kernel team.  After a week, I tested the
newest daily build of the kernel, and the problem still exists.  Sent a
follow-up email with that info, and haven't heard anything.

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

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20354
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
  

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

2018-02-09 Thread DenisP
I have done some further testing and now I can report that resume from
hibernation works for me with 4.15 mainline kernels. Only that my X11
session crashes upon resume from hibernation because of a segmentation
fault in libinput.so. It seems that this crash in X11 is not related to
this bug.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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


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

2018-02-09 Thread Lucas Zanella
Is it possible to boot the live installation media with the kernel
parameter? I'm having problems installing the ubuntu into the new SSD,
always get I/O errors...

I'm gonna also try the new kernel on the old SSD though

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

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

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

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

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

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

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

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

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

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

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-09 Thread Joseph Salisbury
I'm bisecting through the config files manually.  I have two test
kenrels, one should be good and one should be bad.  The test kernels are
available here:

http://kernel.ubuntu.com/~jsalisbury/lp1745342/top-half
http://kernel.ubuntu.com/~jsalisbury/lp1745342/bottom-half

What I'm doing is building a v4.13-rc1 test kernel using just the top
half of the new kernel config options and using the bottom half of the
config file for the other test kernel.  Depending on which one shows the
bug, I'll then divide the bad config file in half again.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+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 1747750] Re: [LENOVO 20KSCTO1WW] hibernate/resume failure

2018-02-09 Thread Sebastiaan Breedveld
Ok, tested with 4.15.0-041500-generic #201802011154.

The good news is that s2disk hibernate still works. However, the kernel
version not. On waking up, the system asks for the cryptswap password,
then mentions "resuming from /dev/mapper/cryptswap1". However, resuming
fails and system is booted as if no hibernation was used.

I also cannot find any error messages or mentions in the logfiles
either.

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

Title:
  [LENOVO 20KSCTO1WW] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) cat /proc/version_signature > version.log

  Ubuntu 4.13.0-32.35-generic 4.13.13

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sebastiaan   1210 F pulseaudio
  Date: Tue Feb  6 17:45:30 2018
  DuplicateSignature: hibernate/resume:LENOVO 20KSCTO1WW:R0PET35W (1.12 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-02-05 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180205)
  InterpreterPath: /usr/bin/python3.6
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:2113 Acer, Inc 
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KSCTO1WW
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=ee28579a-944e-4e9a-81fe-25ecb8b0e802 ro resume=/dev/mapper/cryptswap1
  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.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  Title: [LENOVO 20KSCTO1WW] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET35W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET35W(1.12):bd01/22/2018:svnLENOVO:pn20KSCTO1WW:pvrThinkPadE580:rvnLENOVO:rn20KSCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E580
  dmi.product.name: 20KSCTO1WW
  dmi.product.version: ThinkPad E580
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747750/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

2018-02-09 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1746937] Re: linux-aws: 4.4.0-1013.13 -proposed tracker

2018-02-09 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-aws: 4.4.0-1013.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746937/+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 1250605] Re: 10ec:5286 [Clevo W310CZ] Realtek Card Reader not working.

2018-02-09 Thread Christopher M. Penalver
L'Africain, given this report is about specific hardware not working at all, it 
will help immensely if you use the computer the problem is reproducible with, 
and provide necessary debugging logs by filing a new report with Ubuntu via a 
terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  10ec:5286 [Clevo W310CZ] Realtek Card Reader not working.

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

Bug description:
  I have a Clevo W310CZ. No result when i put a sd card in with ubuntu
  13.10.

  Upstream post: http://marc.info/?l=linux-mmc&m=138774674016006&w=4

  WORKAROUND: In kernel 3.16-rc7, uncomment rtsx_pci in
  /etc/modprobe.d/rtsx_blacklist.conf .

  WORKAROUND: Only in 12.04, as this doesn't work for 13.10:
  1. Download:
  
https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/971876/+attachment/2991730/+files/rts_bpp.tar.bz2
  2. Extract archive, edit rtsx.c:
  2.1. Remove __devinit from rtsx_probe in line 893
  2.2. Remove __devexit from rtsx_remove in line 1048
  2.3. Extract rtsx_remove from __devexit_p() in line 1074
  3. Compile with "make"
  4. As root, make install
  5. Blacklist rtsx_pci in /etc/modprobe.d/rtsx_blacklist.conf (add "blacklist 
rtsx_pci")
  6. 'modprobe rts_bpp'
  7. run mkinitcpio -p linux
  8. Restart the machine

  lsmod
  Module  Size  Used by
  joydev 17377  0
  parport_pc 32701  0
  ppdev  17671  0
  rfcomm 69070  12
  bnep   19564  2
  vesafb 13828  0
  snd_hda_codec_hdmi 41117  1
  snd_hda_codec_via  27860  1
  x86_pkg_temp_thermal14162  0
  intel_powerclamp   14705  0
  coretemp   13435  0
  kvm_intel 138538  0
  kvm   431315  1 kvm_intel
  crct10dif_pclmul   14289  0
  crc32_pclmul   13113  0
  ghash_clmulni_intel13259  0
  cryptd 20329  1 ghash_clmulni_intel
  arc4   12608  2
  snd_hda_intel  48171  3
  snd_hda_codec 188738  3 
snd_hda_codec_hdmi,snd_hda_codec_via,snd_hda_intel
  snd_hwdep  13602  1 snd_hda_codec
  iwldvm237440  0
  snd_pcm   102033  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
  mac80211  596969  1 iwldvm
  microcode  23518  0
  snd_page_alloc 18710  2 snd_pcm,snd_hda_intel
  btusb  28267  0
  bluetooth 371880  22 bnep,btusb,rfcomm
  snd_seq_midi   13324  0
  snd_seq_midi_event 14899  1 snd_seq_midi
  snd_rawmidi30095  1 snd_seq_midi
  snd_seq61560  2 snd_seq_midi_event,snd_seq_midi
  psmouse97626  0
  serio_raw  13413  0
  iwlwifi   165398  1 iwldvm
  lpc_ich21080  0
  cfg80211  479757  3 iwlwifi,mac80211,iwldvm
  wmi19070  0
  snd_seq_device 14497  3 snd_seq,snd_rawmidi,snd_seq_midi
  snd_timer  29433  2 snd_pcm,snd_seq
  i915  655752  3
  drm_kms_helper 52651  1 i915
  video  19318  1 i915
  snd69141  17 
snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_via,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_seq_midi
  drm   296739  4 i915,drm_kms_helper
  mei_me 18421  0
  mei77692  1 mei_me
  i2c_algo_bit   13413  1 i915
  mac_hid13205  0
  soundcore  12680  1 snd
  lp 17759  0
  parport42299  3 lp,ppdev,parport_pc
  r8169  67341  0
  mii13934  1 r8169
  ahci   25819  4
  libahci31898  1 ahci
  ---
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2909 F pulseaudio
  CasperVersion: 1.336ubuntu1
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131222)
  MachineType: Notebook W310CZ
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  Tags:  trusty
  Uname: Linux 3.12.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date

[Kernel-packages] [Bug 1748520] Re: SDXC card reader not recognized

2018-02-09 Thread Wolf Rogner
After a fresh reboot, the device mounts even on encrypted hard disk.

Error has to do with suspend to RAM issues of none-mounting devices.

Should be triaged -> #1744337

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

Title:
  SDXC card reader not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
  is non-responsive.

  uname -a
  Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Installing sdhci and sdhci-pci modules (with or without adding a
  /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
  work.

  After a reboot, the drivers are not installed.
  A device /dev/mmcblk0 is missing.

  This used to be different in previous kernels 4.13... (although I have
  no record when last I tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-33-generic 4.13.0-33.36
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
  Date: Fri Feb  9 20:25:21 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-33-generic N/A
   linux-backports-modules-4.13.0-33-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748520/+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 1746936] Re: linux: 4.4.0-113.136 -proposed tracker

2018-02-09 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux: 4.4.0-113.136 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746936/+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 1744117] Re: ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel

2018-02-09 Thread Khaled El Mously
** Summary changed:

- [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table to 
Ubuntu 16.04 LTS Kernel
+ ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS 
Kernel

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

Title:
  ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu
  16.04 LTS Kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Add support for 4/6/8 channel sound in 16.04 LTS kernel for future
  GPUs.

  This commit[1] first introduced in "Thu Jul 13 19:27:39 2017"[2] has
  what is needed base on discussion we had with nvidia:

  [1] - Commit
   
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f

  ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

  Add codec IDs for several recently released, pending, and historical
  NVIDIA GPU audio controllers to the patch table, to allow the correct
  patch functions to be selected for them.

  [2] - git describe --contains 74ec118152ea494a25ebb677cbc83a75c982ac5f
  v4.13-rc3~21^2~5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744117/+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 1748484] Re: linux: 4.4.0-114.137 -proposed tracker

2018-02-09 Thread Khaled El Mously
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-114.137 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux: 4.4.0-114.137 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1748486 (linux-aws), bug 1748488 (linux-lts-xenial)
  derivatives: bug 1748489 (linux-aws), bug 1748490 (linux-euclid), bug 1748491 
(linux-gke), bug 1748492 (linux-kvm), bug 1748493 (linux-raspi2), bug 1748494 
(linux-snapdragon)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748484/+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 1748520] Re: SDXC card reader not recognized

2018-02-09 Thread Wolf Rogner
On my other MacbookPro 15 the hard disk is encrypted as well but the
device gets mounted to /dev/mmcblk0

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

Title:
  SDXC card reader not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
  is non-responsive.

  uname -a
  Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Installing sdhci and sdhci-pci modules (with or without adding a
  /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
  work.

  After a reboot, the drivers are not installed.
  A device /dev/mmcblk0 is missing.

  This used to be different in previous kernels 4.13... (although I have
  no record when last I tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-33-generic 4.13.0-33.36
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
  Date: Fri Feb  9 20:25:21 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-33-generic N/A
   linux-backports-modules-4.13.0-33-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748520/+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 1748520] Re: SDXC card reader not recognized

2018-02-09 Thread Wolf Rogner
Tested the device with a live USB.
Mounting works fine.

The device is /dev/sdb !!! not /dev/mmcblk0. The device is recognized as
Apple SD Card Reader

The local hard disk on the system is encrypted. Booting from it - the SD
card is not recognized.

Can drive encryption be the reason why mounting a sdx device without
encryption is not possible?

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

Title:
  SDXC card reader not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
  is non-responsive.

  uname -a
  Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Installing sdhci and sdhci-pci modules (with or without adding a
  /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
  work.

  After a reboot, the drivers are not installed.
  A device /dev/mmcblk0 is missing.

  This used to be different in previous kernels 4.13... (although I have
  no record when last I tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-33-generic 4.13.0-33.36
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
  Date: Fri Feb  9 20:25:21 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-33-generic N/A
   linux-backports-modules-4.13.0-33-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748520/+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 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

2018-02-09 Thread Khaled El Mously
** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Committed

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

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-azure source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  New

Bug description:
  == SRU Justification ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers. This 
is a
  regression introduced by commit e0edc8c54646.  This regression is fixed by 
mainline
  commit db5ff909798, which was added to mailine in v4.15-rc9.

  This commit has already been added to Bionic via upstream stable udpates.  
Xenial
  also needs this fix because it recieved the regression introducing commit 
e0edc8c54646
  via the 4.4.48 stable updates(See bug lp1663657).

  
  == Fix ==
  commit db5ff909798ef0099004ad50a0ff5fde92426fd1
  Author: Xinyu Lin 
  Date:   Sun Dec 17 20:13:39 2017 +0800

  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable to fix a regression, so it
  received extra upstream review.

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


  == Original Bug Description ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers.  A 
fix for this issue has been submitted upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  At a high level the root cause of this problem is that the device only
  supports commands with a transfer size up to 512KB.  This worked fine
  with older versions of Linux but newer versions are attempting
  commands with a transfer size of 1280KB which is problematic for this
  device (LITEON EP1-KB480)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743053/+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 1747090] Re: KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

2018-02-09 Thread Khaled El Mously
** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Committed

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

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

Title:
  KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  Mainline commit 35b3fde6203b9 is a KVM patch for s390x to provide facility
  bits 81 (ppa15) and 82 (bpb).  This is required for branch prediction 
behaviour
  changes.

  This is the public bug for SRU.  There is also a priave bug report:
  http://bugs.launchpad.net/bugs/1743560

  There is a qemu portion to this fix:
  http://patchwork.ozlabs.org/cover/862801/

  == Fixes ==
  Artful/Bionic:
  35b3fde6203b ("KVM: s390: wire up bpb feature")

  Xenial:
  ed8dda0bf74b ("Enable all facility bits that are known good for passthrough")
  35b3fde6203b ("KVM: s390: wire up bpb feature")

  
  == Regression Potential ==
  Low, this fix is limited to s390.

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

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

2018-02-09 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/1748520

Title:
  SDXC card reader not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
  is non-responsive.

  uname -a
  Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Installing sdhci and sdhci-pci modules (with or without adding a
  /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
  work.

  After a reboot, the drivers are not installed.
  A device /dev/mmcblk0 is missing.

  This used to be different in previous kernels 4.13... (although I have
  no record when last I tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-33-generic 4.13.0-33.36
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
  Date: Fri Feb  9 20:25:21 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-33-generic N/A
   linux-backports-modules-4.13.0-33-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748520/+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 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

2018-02-09 Thread gagzou
Same: VMs with more than one disk still crash with out of memory. We're using 
Hyper-V on Windows Server 2012 R2 (core) with GEN2 VMs (Ubuntu 16.04 
LTS/Xenial, Kernel 4.4.0-112-generic). VMs with just one disk are running 
perfectly. 
Vss with 1disk ok
Vss with 2disk > freeze with out of memory...

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Tr

[Kernel-packages] [Bug 1748475] Re: linux: 4.13.0-34.37 -proposed tracker

2018-02-09 Thread Khaled El Mously
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.13.0-34.37 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux: 4.13.0-34.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

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

  backports: bug 1748476 (linux-azure), bug 1748477 (linux-azure-edge), bug 
1748478 (linux-gcp), bug 1748479 (linux-hwe), bug 1748480 (linux-hwe-edge), bug 
1748481 (linux-oem)
  derivatives: bug 1748483 (linux-raspi2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748475/+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 1748517] Comment bridged from LTC Bugzilla

2018-02-09 Thread bugproxy
--- Comment From nfont...@us.ibm.com 2018-02-09 14:29 EDT---
Two additional patches to include.

https://marc.info/?l=linux-netdev&m=15181980830&w=2
[PATCH net] ibmvnic: Reset long term map ID counter

https://marc.info/?l=linux-netdev&m=151820439213764&w=2
[PATCH] ibmvnic: Remove skb->protocol checks in ibmvnic_xmit

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

Title:
  Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  We have a number of patches to submit to Canonical for inclusion in
  the their release kernel for Ubuntu 18.04.

  So far, most of these patches are upstream in Linus' tree, with some
  in Dave M's net-next tree.  According to the ubuntu-bionic tree, the
  latest patch included is 8388a6cf ("ibmvnic: Set state UP").  If
  that's true, we'll need about 15 or more patches.  There may be more
  coming down the pipe soon as well.

  Here is a tentative patch list with commit hash and name:

  1. 69d08dc Allocate and request vpd in init_resources
  2. e791380 Revert to previous mtu when unsupported value requested
  3. 896d869 Modify buffer size and number of queues on failover
  4. a0dca10 Fix IPv6 packet descriptors
  5. f689794 Fix IP offload control buffer
  6. 3d16613 Fix pending MAC address changes
  7. 09fb35ead58c Don't handle RX interrupts when not up
  8. 4eb50ceb5c15 Include header descriptor support for ARP packets
  9. 269431e737d2 Increase maximum number of RX/TX queues
  10. d45cc3a43c43 Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES
  11. f743106ec140 fix dma_mapping_error call
  12. 4e6759be28e4 Feature implementation of Vital Product Data (VPD)?
  13. 37798d021131 Add vnic client data to login buffer
  14. 2a1bf597 Fix failover error path for non-fatal resets
  15. c26eba03e407 Update reset infrastructure to support tunable parameters
  16. aa0bf8510dac Let users change net device features
  17. fdb061056f57 Enable TSO support
  18. 154820563dd4 Enable scatter-gather support

  These should apply cleanly, but I'll check on that.

  Thanks!

  
  Here is a tarball of patches.  I also included this patch:

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f813614f531114db796ad66ced75c5dc8db7aa3a

  
  Additional patches that we would like to have included:

  https://marc.info/?l=linux-netdev&m=151803103818174&w=2
  ("[PATCH net-next] ibmvnic: queue reset when CRQ gets closed during reset")

  https://marc.info/?l=linux-netdev&m=151796813926975&w=2
  ("[PATCH net] ibmvnic: Fix rx queue cleanup for non-fatal resets")

  https://marc.info/?l=linux-netdev&m=151631440609769&w=2
  ("[PATCH net v2 1/3] ibmvnic: Modify buffer size and number of queues on 
failover")

  https://marc.info/?l=linux-netdev&m=151631444309775&w=2
  ("[PATCH net v2 2/3] ibmvnic: Revert to previous mtu when unsupported value 
requested")

  https://marc.info/?l=linux-netdev&m=151631448809782&w=2
  ("[PATCH net v2 3/3] ibmvnic: Allocate and request vpd in init_resources")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=d45cc3a43c43f867668bdd7ace12b1e6aa68bf46
  ("ibmvnic: Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=269431e737d29da0f496b60188a580822d290a37
  ("ibmvnic: Increase maximum number of RX/TX queues")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=4eb50ceb5c156a166c0b00ac27f0ff3a0943cdfb
  ("ibmvnic: Include header descriptor support for ARP packets")

  https://marc.info/?l=linux-netdev&m=151796813526938&w=2
   [PATCH net] ibmvnic: Ensure that buffers are NULL after free

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1748517/+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 1748520] [NEW] SDXC card reader not recognized

2018-02-09 Thread Wolf Rogner
Public bug reported:

On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
is non-responsive.

uname -a
Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

Installing sdhci and sdhci-pci modules (with or without adding a
/etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
work.

After a reboot, the drivers are not installed.
A device /dev/mmcblk0 is missing.

This used to be different in previous kernels 4.13... (although I have
no record when last I tested).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-33-generic 4.13.0-33.36
ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
Uname: Linux 4.13.0-33-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1055 F pulseaudio
  wolf   1399 F pulseaudio
 /dev/snd/controlC0:  gdm1055 F pulseaudio
  wolf   1399 F pulseaudio
Date: Fri Feb  9 20:25:21 2018
HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
InstallationDate: Installed on 2017-10-20 (112 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-33-generic N/A
 linux-backports-modules-4.13.0-33-generic  N/A
 linux-firmware 1.169.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0171.B00.1708080033
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug artful package-from-proposed

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

Title:
  SDXC card reader not recognized

Status in linux package in Ubuntu:
  New

Bug description:
  On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
  is non-responsive.

  uname -a
  Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Installing sdhci and sdhci-pci modules (with or without adding a
  /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
  work.

  After a reboot, the drivers are not installed.
  A device /dev/mmcblk0 is missing.

  This used to be different in previous kernels 4.13... (although I have
  no record when last I tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-33-generic 4.13.0-33.36
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
  Date: Fri Feb  9 20:25:21 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] 

[Kernel-packages] [Bug 1748517] Re: Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

2018-02-09 Thread Andrew Cloke
** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  We have a number of patches to submit to Canonical for inclusion in
  the their release kernel for Ubuntu 18.04.

  So far, most of these patches are upstream in Linus' tree, with some
  in Dave M's net-next tree.  According to the ubuntu-bionic tree, the
  latest patch included is 8388a6cf ("ibmvnic: Set state UP").  If
  that's true, we'll need about 15 or more patches.  There may be more
  coming down the pipe soon as well.

  Here is a tentative patch list with commit hash and name:

  1. 69d08dc Allocate and request vpd in init_resources
  2. e791380 Revert to previous mtu when unsupported value requested
  3. 896d869 Modify buffer size and number of queues on failover
  4. a0dca10 Fix IPv6 packet descriptors
  5. f689794 Fix IP offload control buffer
  6. 3d16613 Fix pending MAC address changes
  7. 09fb35ead58c Don't handle RX interrupts when not up
  8. 4eb50ceb5c15 Include header descriptor support for ARP packets
  9. 269431e737d2 Increase maximum number of RX/TX queues
  10. d45cc3a43c43 Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES
  11. f743106ec140 fix dma_mapping_error call
  12. 4e6759be28e4 Feature implementation of Vital Product Data (VPD)?
  13. 37798d021131 Add vnic client data to login buffer
  14. 2a1bf597 Fix failover error path for non-fatal resets
  15. c26eba03e407 Update reset infrastructure to support tunable parameters
  16. aa0bf8510dac Let users change net device features
  17. fdb061056f57 Enable TSO support
  18. 154820563dd4 Enable scatter-gather support

  These should apply cleanly, but I'll check on that.

  Thanks!

  
  Here is a tarball of patches.  I also included this patch:

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f813614f531114db796ad66ced75c5dc8db7aa3a

  
  Additional patches that we would like to have included:

  https://marc.info/?l=linux-netdev&m=151803103818174&w=2
  ("[PATCH net-next] ibmvnic: queue reset when CRQ gets closed during reset")

  https://marc.info/?l=linux-netdev&m=151796813926975&w=2
  ("[PATCH net] ibmvnic: Fix rx queue cleanup for non-fatal resets")

  https://marc.info/?l=linux-netdev&m=151631440609769&w=2
  ("[PATCH net v2 1/3] ibmvnic: Modify buffer size and number of queues on 
failover")

  https://marc.info/?l=linux-netdev&m=151631444309775&w=2
  ("[PATCH net v2 2/3] ibmvnic: Revert to previous mtu when unsupported value 
requested")

  https://marc.info/?l=linux-netdev&m=151631448809782&w=2
  ("[PATCH net v2 3/3] ibmvnic: Allocate and request vpd in init_resources")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=d45cc3a43c43f867668bdd7ace12b1e6aa68bf46
  ("ibmvnic: Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=269431e737d29da0f496b60188a580822d290a37
  ("ibmvnic: Increase maximum number of RX/TX queues")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=4eb50ceb5c156a166c0b00ac27f0ff3a0943cdfb
  ("ibmvnic: Include header descriptor support for ARP packets")

  https://marc.info/?l=linux-netdev&m=151796813526938&w=2
   [PATCH net] ibmvnic: Ensure that buffers are NULL after free

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1748517/+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 1748517] tarball of patches

2018-02-09 Thread bugproxy
Default Comment by Bridge

** Attachment added: "tarball of patches"
   
https://bugs.launchpad.net/bugs/1748517/+attachment/5052092/+files/vnic-patches.tar.gz

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

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

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

Title:
  Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  We have a number of patches to submit to Canonical for inclusion in
  the their release kernel for Ubuntu 18.04.

  So far, most of these patches are upstream in Linus' tree, with some
  in Dave M's net-next tree.  According to the ubuntu-bionic tree, the
  latest patch included is 8388a6cf ("ibmvnic: Set state UP").  If
  that's true, we'll need about 15 or more patches.  There may be more
  coming down the pipe soon as well.

  Here is a tentative patch list with commit hash and name:

  1. 69d08dc Allocate and request vpd in init_resources
  2. e791380 Revert to previous mtu when unsupported value requested
  3. 896d869 Modify buffer size and number of queues on failover
  4. a0dca10 Fix IPv6 packet descriptors
  5. f689794 Fix IP offload control buffer
  6. 3d16613 Fix pending MAC address changes
  7. 09fb35ead58c Don't handle RX interrupts when not up
  8. 4eb50ceb5c15 Include header descriptor support for ARP packets
  9. 269431e737d2 Increase maximum number of RX/TX queues
  10. d45cc3a43c43 Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES
  11. f743106ec140 fix dma_mapping_error call
  12. 4e6759be28e4 Feature implementation of Vital Product Data (VPD)?
  13. 37798d021131 Add vnic client data to login buffer
  14. 2a1bf597 Fix failover error path for non-fatal resets
  15. c26eba03e407 Update reset infrastructure to support tunable parameters
  16. aa0bf8510dac Let users change net device features
  17. fdb061056f57 Enable TSO support
  18. 154820563dd4 Enable scatter-gather support

  These should apply cleanly, but I'll check on that.

  Thanks!

  
  Here is a tarball of patches.  I also included this patch:

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f813614f531114db796ad66ced75c5dc8db7aa3a

  
  Additional patches that we would like to have included:

  https://marc.info/?l=linux-netdev&m=151803103818174&w=2
  ("[PATCH net-next] ibmvnic: queue reset when CRQ gets closed during reset")

  https://marc.info/?l=linux-netdev&m=151796813926975&w=2
  ("[PATCH net] ibmvnic: Fix rx queue cleanup for non-fatal resets")

  https://marc.info/?l=linux-netdev&m=151631440609769&w=2
  ("[PATCH net v2 1/3] ibmvnic: Modify buffer size and number of queues on 
failover")

  https://marc.info/?l=linux-netdev&m=151631444309775&w=2
  ("[PATCH net v2 2/3] ibmvnic: Revert to previous mtu when unsupported value 
requested")

  https://marc.info/?l=linux-netdev&m=151631448809782&w=2
  ("[PATCH net v2 3/3] ibmvnic: Allocate and request vpd in init_resources")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=d45cc3a43c43f867668bdd7ace12b1e6aa68bf46
  ("ibmvnic: Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=269431e737d29da0f496b60188a580822d290a37
  ("ibmvnic: Increase maximum number of RX/TX queues")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=4eb50ceb5c156a166c0b00ac27f0ff3a0943cdfb
  ("ibmvnic: Include header descriptor support for ARP packets")

  https://marc.info/?l=linux-netdev&m=151796813526938&w=2
   [PATCH net] ibmvnic: Ensure that buffers are NULL after free

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1748517/+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 1748517] [NEW] Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

2018-02-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

We have a number of patches to submit to Canonical for inclusion in the
their release kernel for Ubuntu 18.04.

So far, most of these patches are upstream in Linus' tree, with some in
Dave M's net-next tree.  According to the ubuntu-bionic tree, the latest
patch included is 8388a6cf ("ibmvnic: Set state UP").  If that's true,
we'll need about 15 or more patches.  There may be more coming down the
pipe soon as well.

Here is a tentative patch list with commit hash and name:

1. 69d08dc Allocate and request vpd in init_resources
2. e791380 Revert to previous mtu when unsupported value requested
3. 896d869 Modify buffer size and number of queues on failover
4. a0dca10 Fix IPv6 packet descriptors
5. f689794 Fix IP offload control buffer
6. 3d16613 Fix pending MAC address changes
7. 09fb35ead58c Don't handle RX interrupts when not up
8. 4eb50ceb5c15 Include header descriptor support for ARP packets
9. 269431e737d2 Increase maximum number of RX/TX queues
10. d45cc3a43c43 Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES
11. f743106ec140 fix dma_mapping_error call
12. 4e6759be28e4 Feature implementation of Vital Product Data (VPD)?
13. 37798d021131 Add vnic client data to login buffer
14. 2a1bf597 Fix failover error path for non-fatal resets
15. c26eba03e407 Update reset infrastructure to support tunable parameters
16. aa0bf8510dac Let users change net device features
17. fdb061056f57 Enable TSO support
18. 154820563dd4 Enable scatter-gather support

These should apply cleanly, but I'll check on that.

Thanks!


Here is a tarball of patches.  I also included this patch:

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=f813614f531114db796ad66ced75c5dc8db7aa3a


Additional patches that we would like to have included:

https://marc.info/?l=linux-netdev&m=151803103818174&w=2
("[PATCH net-next] ibmvnic: queue reset when CRQ gets closed during reset")

https://marc.info/?l=linux-netdev&m=151796813926975&w=2
("[PATCH net] ibmvnic: Fix rx queue cleanup for non-fatal resets")

https://marc.info/?l=linux-netdev&m=151631440609769&w=2
("[PATCH net v2 1/3] ibmvnic: Modify buffer size and number of queues on 
failover")

https://marc.info/?l=linux-netdev&m=151631444309775&w=2
("[PATCH net v2 2/3] ibmvnic: Revert to previous mtu when unsupported value 
requested")

https://marc.info/?l=linux-netdev&m=151631448809782&w=2
("[PATCH net v2 3/3] ibmvnic: Allocate and request vpd in init_resources")

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=d45cc3a43c43f867668bdd7ace12b1e6aa68bf46
("ibmvnic: Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES")

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=269431e737d29da0f496b60188a580822d290a37
("ibmvnic: Increase maximum number of RX/TX queues")

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=4eb50ceb5c156a166c0b00ac27f0ff3a0943cdfb
("ibmvnic: Include header descriptor support for ARP packets")

https://marc.info/?l=linux-netdev&m=151796813526938&w=2
 [PATCH net] ibmvnic: Ensure that buffers are NULL after free

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


** Tags: architecture-ppc64le bugnameltc-163890 severity-high 
targetmilestone-inin1804
-- 
Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel
https://bugs.launchpad.net/bugs/1748517
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 1250605] Re: 10ec:5286 [Clevo W310CZ] Realtek Card Reader not working.

2018-02-09 Thread L'Africain
Hello,
On Ubuntu 16.04 I can read but not write.

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

Title:
  10ec:5286 [Clevo W310CZ] Realtek Card Reader not working.

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

Bug description:
  I have a Clevo W310CZ. No result when i put a sd card in with ubuntu
  13.10.

  Upstream post: http://marc.info/?l=linux-mmc&m=138774674016006&w=4

  WORKAROUND: In kernel 3.16-rc7, uncomment rtsx_pci in
  /etc/modprobe.d/rtsx_blacklist.conf .

  WORKAROUND: Only in 12.04, as this doesn't work for 13.10:
  1. Download:
  
https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/971876/+attachment/2991730/+files/rts_bpp.tar.bz2
  2. Extract archive, edit rtsx.c:
  2.1. Remove __devinit from rtsx_probe in line 893
  2.2. Remove __devexit from rtsx_remove in line 1048
  2.3. Extract rtsx_remove from __devexit_p() in line 1074
  3. Compile with "make"
  4. As root, make install
  5. Blacklist rtsx_pci in /etc/modprobe.d/rtsx_blacklist.conf (add "blacklist 
rtsx_pci")
  6. 'modprobe rts_bpp'
  7. run mkinitcpio -p linux
  8. Restart the machine

  lsmod
  Module  Size  Used by
  joydev 17377  0
  parport_pc 32701  0
  ppdev  17671  0
  rfcomm 69070  12
  bnep   19564  2
  vesafb 13828  0
  snd_hda_codec_hdmi 41117  1
  snd_hda_codec_via  27860  1
  x86_pkg_temp_thermal14162  0
  intel_powerclamp   14705  0
  coretemp   13435  0
  kvm_intel 138538  0
  kvm   431315  1 kvm_intel
  crct10dif_pclmul   14289  0
  crc32_pclmul   13113  0
  ghash_clmulni_intel13259  0
  cryptd 20329  1 ghash_clmulni_intel
  arc4   12608  2
  snd_hda_intel  48171  3
  snd_hda_codec 188738  3 
snd_hda_codec_hdmi,snd_hda_codec_via,snd_hda_intel
  snd_hwdep  13602  1 snd_hda_codec
  iwldvm237440  0
  snd_pcm   102033  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
  mac80211  596969  1 iwldvm
  microcode  23518  0
  snd_page_alloc 18710  2 snd_pcm,snd_hda_intel
  btusb  28267  0
  bluetooth 371880  22 bnep,btusb,rfcomm
  snd_seq_midi   13324  0
  snd_seq_midi_event 14899  1 snd_seq_midi
  snd_rawmidi30095  1 snd_seq_midi
  snd_seq61560  2 snd_seq_midi_event,snd_seq_midi
  psmouse97626  0
  serio_raw  13413  0
  iwlwifi   165398  1 iwldvm
  lpc_ich21080  0
  cfg80211  479757  3 iwlwifi,mac80211,iwldvm
  wmi19070  0
  snd_seq_device 14497  3 snd_seq,snd_rawmidi,snd_seq_midi
  snd_timer  29433  2 snd_pcm,snd_seq
  i915  655752  3
  drm_kms_helper 52651  1 i915
  video  19318  1 i915
  snd69141  17 
snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_via,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_seq_midi
  drm   296739  4 i915,drm_kms_helper
  mei_me 18421  0
  mei77692  1 mei_me
  i2c_algo_bit   13413  1 i915
  mac_hid13205  0
  soundcore  12680  1 snd
  lp 17759  0
  parport42299  3 lp,ppdev,parport_pc
  r8169  67341  0
  mii13934  1 r8169
  ahci   25819  4
  libahci31898  1 ahci
  ---
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2909 F pulseaudio
  CasperVersion: 1.336ubuntu1
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131222)
  MachineType: Notebook W310CZ
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  Tags:  trusty
  Uname: Linux 3.12.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W310CZ
  dmi.board.vendor: Notebook
  dmi.board.version: V2.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
 

[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2018-02-09 Thread Peridot
Though with iommu=soft it boots on both kernels with IOMMU and AMD-v
enabled in the BIOS

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2018-02-09 Thread Peridot
And with the mainline kernel

** Attachment added: "amdv and iommu enabled mainline kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/+attachment/5052087/+files/mainland.jpg

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/+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 1748513] [NEW] BUG: unable to handle kernel paging request at 00007f29ec101010

2018-02-09 Thread Simon Déziel
Public bug reported:

Got this bug/oops while running with the linux-image-4.4.0-113-generic
(4.4.0-113.136) kernel from -proposed:

BUG: unable to handle kernel paging request at 7f29ec101010
IP: [] csum_and_copy_from_iter+0x55/0x4c0
PGD 82fcef6f9067 PUD 2fd1615e067 PMD 2fcef77e067 PTE 82fd0009f867
Oops: 0001 [#1] SMP 
Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_
 fjes wmi
CPU: 39 PID: 27347 Comm: fping Not tainted 4.4.0-113-generic #136-Ubuntu
Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
task: 88bd1125e200 ti: 897d0285 task.ti: 897d0285
RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
RSP: 0018:897d02853a18  EFLAGS: 00010246
RAX: 0018 RBX: 0006 RCX: 897d02853e98
RDX: 897d02853a94 RSI: 0040 RDI: 8afcfba4ea24
RBP: 897d02853a80 R08:  R09: 8afcfba4ea24
R10: 8afcfba4ea24 R11: 8afcfba4ea00 R12: 897d02853e98
R13:  R14: 1ee730fc3e9fb34c R15: 7f29ec101008
FS:  7f29ec282700() GS:8afd7ec4() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7f29ec101010 CR3: 02fce5462000 CR4: 00360670
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
Stack:
 88bd7ec07340 9772d1d7 8afcf02d8f00 897d02853aaf
 897d02853a94 01c0  1ee730fc3e9fb34c
 0040 8afcf02d8f00  897d02853d30
Call Trace:
 [] ? __alloc_skb+0x87/0x1f0
 [] ip_generic_getfrag+0x56/0xe0
 [] raw_getfrag+0xaf/0x100
 [] __ip_append_data.isra.45+0x98a/0xb90
 [] ? raw_recvmsg+0x1c0/0x1c0
 [] ? raw_recvmsg+0x1c0/0x1c0
 [] ip_append_data.part.46+0x7a/0xe0
 [] ip_append_data+0x34/0x40
 [] raw_sendmsg+0x724/0xc00
 [] ? aa_sk_perm+0x70/0x210
 [] ? aa_sock_msg_perm+0x61/0x150
 [] inet_sendmsg+0x6b/0xa0
 [] sock_sendmsg+0x3e/0x50
 [] SYSC_sendto+0x101/0x190
 [] ? vm_mmap_pgoff+0xbb/0xe0
 [] ? __do_page_fault+0x1b4/0x400
 [] SyS_sendto+0xe/0x10
 [] entry_SYSCALL_64_fastpath+0x1c/0x93
Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
RIP  [] csum_and_copy_from_iter+0x55/0x4c0
 RSP 
CR2: 7f29ec101010
---[ end trace 48102008d03cb384 ]---

This is something new with the -proposed kernel.

Additional information:

$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

$ apt-cache policy linux-image-4.4.0-113-generic
linux-image-4.4.0-113-generic:
  Installed: 4.4.0-113.136
  Candidate: 4.4.0-113.136
  Version table:
 *** 4.4.0-113.136 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-113-generic 4.4.0-113.136
ProcVersionSignature: Ubuntu 4.4.0-113.136-generic 4.4.98
Uname: Linux 4.4.0-113-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Feb  9 10:45 seq
 crw-rw 1 root audio 116, 33 Feb  9 10:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
Date: Fri Feb  9 13:41:20 2018
HibernationDevice: RESUME=/dev/mapper/vghost-swap
InstallationDate: Installed on 2017-04-01 (314 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:8002 Intel Corp. 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
 Bus 001 Device 002: ID 8087:800a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R830
PciMultimedia:
 
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-113-generic.efi.signed 
root=/dev/mapper/vghost-root ro panic=300 kaslr vsyscall=none
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-113-generic N/A
 linux-backports-modules-4.4.0-113-generic  N/A
 linux-firmware 1.157.15
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.4
dmi.board.name: 0VVT0H
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd11/09/2016:svnDell

[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2018-02-09 Thread Peridot
AMD-v was not enabled but with it enabled booting without iommu=soft
results in a crash that only lasts about a second and then loses HDMI
connection. This is with the Ubuntu Kernel

** Attachment added: "amdv and iommu enabled ubuntu kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/+attachment/5052073/+files/ubuntukernel.jpg

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

2018-02-09 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/1748513

Title:
  BUG: unable to handle kernel paging request at 7f29ec101010

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel paging request at 7f29ec101010
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 82fcef6f9067 PUD 2fd1615e067 PMD 2fcef77e067 PTE 82fd0009f867
  Oops: 0001 [#1] SMP 
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_
   fjes wmi
  CPU: 39 PID: 27347 Comm: fping Not tainted 4.4.0-113-generic #136-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
  task: 88bd1125e200 ti: 897d0285 task.ti: 897d0285
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:897d02853a18  EFLAGS: 00010246
  RAX: 0018 RBX: 0006 RCX: 897d02853e98
  RDX: 897d02853a94 RSI: 0040 RDI: 8afcfba4ea24
  RBP: 897d02853a80 R08:  R09: 8afcfba4ea24
  R10: 8afcfba4ea24 R11: 8afcfba4ea00 R12: 897d02853e98
  R13:  R14: 1ee730fc3e9fb34c R15: 7f29ec101008
  FS:  7f29ec282700() GS:8afd7ec4() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f29ec101010 CR3: 02fce5462000 CR4: 00360670
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88bd7ec07340 9772d1d7 8afcf02d8f00 897d02853aaf
   897d02853a94 01c0  1ee730fc3e9fb34c
   0040 8afcf02d8f00  897d02853d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x7a/0xe0
   [] ip_append_data+0x34/0x40
   [] raw_sendmsg+0x724/0xc00
   [] ? aa_sk_perm+0x70/0x210
   [] ? aa_sock_msg_perm+0x61/0x150
   [] inet_sendmsg+0x6b/0xa0
   [] sock_sendmsg+0x3e/0x50
   [] SYSC_sendto+0x101/0x190
   [] ? vm_mmap_pgoff+0xbb/0xe0
   [] ? __do_page_fault+0x1b4/0x400
   [] SyS_sendto+0xe/0x10
   [] entry_SYSCALL_64_fastpath+0x1c/0x93
  Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
  RIP  [] csum_and_copy_from_iter+0x55/0x4c0
   RSP 
  CR2: 7f29ec101010
  ---[ end trace 48102008d03cb384 ]---

  This is something new with the -proposed kernel.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  $ apt-cache policy linux-image-4.4.0-113-generic
  linux-image-4.4.0-113-generic:
Installed: 4.4.0-113.136
Candidate: 4.4.0-113.136
Version table:
   *** 4.4.0-113.136 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-113-generic 4.4.0-113.136
  ProcVersionSignature: Ubuntu 4.4.0-113.136-generic 4.4.98
  Uname: Linux 4.4.0-113-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  9 10:45 seq
   crw-rw 1 root audio 116, 33 Feb  9 10:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Fri Feb  9 13:41:20 2018
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (314 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R830
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-113-generic.efi.signed 
root=/dev/mapper/vghost-root ro panic=300 kaslr vsyscall=none
  RelatedPackageVe

[Kernel-packages] [Bug 1748487] Re: Please upgrade to get kernel management

2018-02-09 Thread dino99
** Tags added: bot-stop-nagging

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

Title:
  Please upgrade to get  kernel management

Status in acpi-support package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bionic still has that old version from 2013
  Debian have a more recent version: 
http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog
  Actual source: http://www.uefi.org/acpi

  Kernel (upstream) is supposed to have fixed the problem:
  
https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195

  Does ubuntu kernel apply that patch ?
  https://bugzilla.kernel.org/show_bug.cgi?id=117671

  Because kernel 4.15.0-9 still log these errors:

  kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170831/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170831/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20170831/tbxfload-246)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: acpi-support 0.142
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  9 17:49:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1748487/+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 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2018-02-09 Thread Kai-Heng Feng
Build a new one, based on artful,

http://people.canonical.com/~khfeng/lp1746340-artful/

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  A user reported his NVMe went out to lunch after S3.

  [Fix]
  Disable APST for this particular NVMe + Motherboard setup.

  [Test]
  User confirmed this quirk works for his system.

  [Regression Potential]
  Very Low. This applies to a specific device setup, also user can
  override this quirk by "nvme_core.force_apst=1".

  === Original Bug Report ===
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
    rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
    rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
    rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
    rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
    rwt:4 rwl:4 idle_power:- active_power:-
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.

   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or n

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

2018-02-09 Thread Kai-Heng Feng
You need to boot with kernel parameter
"nvme_core.default_ps_max_latency_us=0"

Please try this kernel after installation:
http://people.canonical.com/~khfeng/lp1746340-artful/

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

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

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

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

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

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

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

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

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

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

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

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

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

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

2018-02-09 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/1748505

Title:
  Boot failed with hard LOCKUP linux-image-4.4.0-112

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting this kernel ended with

  [35.111831] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1
  [36.073026] NMI watchdog: Watchdog detected hard LOCKUP on cpu 2
  [36.153549] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
  [36.451526] NMI watchdog: Watchdog detected hard LOCKUP on cpu 3 

  Booting previous kernel linux-image-4.4.0-109-generic is working
  smoothly as well as previous ones.

  cat /proc/version_signature = Ubuntu 4.4.0-109.132-generic 4.4.98

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dh 2583 F pulseaudio
   /dev/snd/controlC1:  dh 2583 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  9 19:02:26 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  HibernationDevice: RESUME=UUID=103ed14e-e6b6-49d5-a28f-020343e6a118
  InstallationDate: Installed on 2013-10-13 (1580 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=8a01ac20-42e5-49f3-b385-674e05cd8d7c ro quiet splash 
acpi_rev_override=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-10-05 (491 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0JNYGR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd12/15/2017:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0JNYGR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748505/+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 1748505] [NEW] Boot failed with hard LOCKUP linux-image-4.4.0-112

2018-02-09 Thread Dash
Public bug reported:

Booting this kernel ended with

[35.111831] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1
[36.073026] NMI watchdog: Watchdog detected hard LOCKUP on cpu 2
[36.153549] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
[36.451526] NMI watchdog: Watchdog detected hard LOCKUP on cpu 3 

Booting previous kernel linux-image-4.4.0-109-generic is working
smoothly as well as previous ones.

cat /proc/version_signature = Ubuntu 4.4.0-109.132-generic 4.4.98

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-112-generic 4.4.0-112.135
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dh 2583 F pulseaudio
 /dev/snd/controlC1:  dh 2583 F pulseaudio
CurrentDesktop: Unity
Date: Fri Feb  9 19:02:26 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
HibernationDevice: RESUME=UUID=103ed14e-e6b6-49d5-a28f-020343e6a118
InstallationDate: Installed on 2013-10-13 (1580 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
MachineType: Dell Inc. Latitude E7440
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=8a01ac20-42e5-49f3-b385-674e05cd8d7c ro quiet splash 
acpi_rev_override=1
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-109-generic N/A
 linux-backports-modules-4.4.0-109-generic  N/A
 linux-firmware 1.157.15
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-10-05 (491 days ago)
dmi.bios.date: 12/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A23
dmi.board.name: 0JNYGR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd12/15/2017:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0JNYGR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug linux-image xenial

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

Title:
  Boot failed with hard LOCKUP linux-image-4.4.0-112

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Booting this kernel ended with

  [35.111831] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1
  [36.073026] NMI watchdog: Watchdog detected hard LOCKUP on cpu 2
  [36.153549] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
  [36.451526] NMI watchdog: Watchdog detected hard LOCKUP on cpu 3 

  Booting previous kernel linux-image-4.4.0-109-generic is working
  smoothly as well as previous ones.

  cat /proc/version_signature = Ubuntu 4.4.0-109.132-generic 4.4.98

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dh 2583 F pulseaudio
   /dev/snd/controlC1:  dh 2583 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  9 19:02:26 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  HibernationDevice: RESUME=UUID=103ed14e-e6b6-49d5-a28f-020343e6a118
  InstallationDate: Installed on 2013-10-13 (1580 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=8a01ac20-42e5-49f3-b385-674e05cd8d7c ro quiet splash 
acpi_rev_override=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-10-05 (491 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0JNYGR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd12/15/2017:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0JNYGR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage noti

[Kernel-packages] [Bug 1655085] Re: bugs linux 64bits and intel hd graphics card 4600

2018-02-09 Thread Mehdinefrance
Unfortunately, the bug is still here. Even after I install "linux-
headers-4.15.1-041501_4.15.1-041501.201802031831_all.deb" package.

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

Title:
  bugs linux 64bits and intel hd graphics card 4600

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  I just bought Euler 4785T and a 27" Iiyama ProLite X2783HSU-B1 screen.

  When trying to install Ubuntu/Xubuntu 16.04 or 16.10 (32 or 64bits) I
  have some display problems (brightness button is blocked, right-click
  in Firefox bugs...)

  Same problem with Linux Mint 17 and 18 (64bits), but so far, it seems
  to work with Linux Mint XFCE 32 bits.

  I wrote a post in Ubuntu forum (in French) here : http://forum.ubuntu-
  fr.org/viewtopic.php?pid=21657030#p21657030.

  I have been told to report the bug on Launchpad. It may be helpful.

  Don't hesitate to ask me for details.

  Best regards.

  
  Intel HD Graphics 4600
  Intel H87
  Intel Core i7 4785T
  Hardware : SSD 500Go
  Memory : 16 Go
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CasperVersion: 1.379
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Q87T
  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.:bvr1001:bd08/15/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnQ87T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655085/+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 1748503] Re: Eject can't find second CD/DVD drive

2018-02-09 Thread david braun
Here is the strace output for "eject -v -X sr0" for comparison

** Attachment added: "strace output for "eject -v -X sr0""
   
https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1748503/+attachment/5052019/+files/sr0.trace

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

Title:
  Eject can't find second CD/DVD drive

Status in eject package in Ubuntu:
  New

Bug description:
  My machine has two CD/DVD drives. Entering "eject -v -X sr0" finds the
  first drive. Entering "eject -v -X sr1" sorta finds the second drive
  but not really. Here's the output for both.

  $ eject -v -X sr0
  eject: device name is `sr0'
  eject: expanded name is `/dev/sr0'
  eject: `/dev/sr0' is not mounted
  eject: `/dev/sr0' is not a mount point
  eject: listing CD-ROM speed
  eject: saving original speed 48
  48 
  eject: restored original speed 48
  $ eject -v -X sr1
  eject: device name is `sr1'
  eject: expanded name is `/dev/sr1'
  eject: `/dev/sr1' is not mounted
  eject: `/dev/sr1' is not a mount point
  eject: listing CD-ROM speed
  eject: error while finding CD-ROM name
  $ 

  Actually ejecting the drive with "eject sr0" or "eject sr1" works
  fine. Running the command under strace shows an attempt to open
  "/dev/sr" which is probably wrong.

  $ strace eject -v -X sr1
  execve("/usr/bin/eject", ["eject", "-v", "-X", "sr1"], [/* 66 vars */]) = 0
  brk(NULL)   = 0x55a4775a
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
.
.
.
  geteuid()   = 1000
  open("/dev/sr1", O_RDWR|O_NONBLOCK) = 3
  open("/proc/sys/dev/cdrom/info", O_RDONLY) = 4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "CD-ROM information, Id: cdrom.c "..., 1024) = 476
  readlink("/dev/sr", 0x7ffc1f7cede8, 4095) = -1 ENOENT (No such file or 
directory)
  write(2, "eject: error while finding CD-RO"..., 39eject: error while finding 
CD-ROM name
  ) = 39
  lseek(4, -406, SEEK_CUR)= 70
  exit_group(1)   = ?
  +++ exited with 1 +++
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  9 12:42:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-01-30 (9 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: eject
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1748503/+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 1748503] [NEW] Eject can't find second CD/DVD drive

2018-02-09 Thread david braun
Public bug reported:

My machine has two CD/DVD drives. Entering "eject -v -X sr0" finds the
first drive. Entering "eject -v -X sr1" sorta finds the second drive but
not really. Here's the output for both.

$ eject -v -X sr0
eject: device name is `sr0'
eject: expanded name is `/dev/sr0'
eject: `/dev/sr0' is not mounted
eject: `/dev/sr0' is not a mount point
eject: listing CD-ROM speed
eject: saving original speed 48
48 
eject: restored original speed 48
$ eject -v -X sr1
eject: device name is `sr1'
eject: expanded name is `/dev/sr1'
eject: `/dev/sr1' is not mounted
eject: `/dev/sr1' is not a mount point
eject: listing CD-ROM speed
eject: error while finding CD-ROM name
$ 

Actually ejecting the drive with "eject sr0" or "eject sr1" works fine.
Running the command under strace shows an attempt to open "/dev/sr"
which is probably wrong.

$ strace eject -v -X sr1
execve("/usr/bin/eject", ["eject", "-v", "-X", "sr1"], [/* 66 vars */]) = 0
brk(NULL)   = 0x55a4775a
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
  .
  .
  .
geteuid()   = 1000
open("/dev/sr1", O_RDWR|O_NONBLOCK) = 3
open("/proc/sys/dev/cdrom/info", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(4, "CD-ROM information, Id: cdrom.c "..., 1024) = 476
readlink("/dev/sr", 0x7ffc1f7cede8, 4095) = -1 ENOENT (No such file or 
directory)
write(2, "eject: error while finding CD-RO"..., 39eject: error while finding 
CD-ROM name
) = 39
lseek(4, -406, SEEK_CUR)= 70
exit_group(1)   = ?
+++ exited with 1 +++
$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb  9 12:42:30 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-01-30 (9 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: eject
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "strace output for "eject -v -X sr1""
   https://bugs.launchpad.net/bugs/1748503/+attachment/5052014/+files/sr1.trace

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

Title:
  Eject can't find second CD/DVD drive

Status in eject package in Ubuntu:
  New

Bug description:
  My machine has two CD/DVD drives. Entering "eject -v -X sr0" finds the
  first drive. Entering "eject -v -X sr1" sorta finds the second drive
  but not really. Here's the output for both.

  $ eject -v -X sr0
  eject: device name is `sr0'
  eject: expanded name is `/dev/sr0'
  eject: `/dev/sr0' is not mounted
  eject: `/dev/sr0' is not a mount point
  eject: listing CD-ROM speed
  eject: saving original speed 48
  48 
  eject: restored original speed 48
  $ eject -v -X sr1
  eject: device name is `sr1'
  eject: expanded name is `/dev/sr1'
  eject: `/dev/sr1' is not mounted
  eject: `/dev/sr1' is not a mount point
  eject: listing CD-ROM speed
  eject: error while finding CD-ROM name
  $ 

  Actually ejecting the drive with "eject sr0" or "eject sr1" works
  fine. Running the command under strace shows an attempt to open
  "/dev/sr" which is probably wrong.

  $ strace eject -v -X sr1
  execve("/usr/bin/eject", ["eject", "-v", "-X", "sr1"], [/* 66 vars */]) = 0
  brk(NULL)   = 0x55a4775a
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
.
.
.
  geteuid()   = 1000
  open("/dev/sr1", O_RDWR|O_NONBLOCK) = 3
  open("/proc/sys/dev/cdrom/info", O_RDONLY) = 4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "CD-ROM information, Id: cdrom.c "..., 1024) = 476
  readlink("/dev/sr", 0x7ffc1f7cede8, 4095) = -1 ENOENT (No such file or 
directory)
  write(2, "eject: error while finding CD-RO"..., 39eject: error while finding 
CD-ROM name
  ) = 39
  lseek(4, -406, SEEK_CUR)= 70
  exit_group(1)   = ?
  +++ exited with 1 +++
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  9 12:42:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-01-30 (9 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: eject
  UpgradeStatus: No upgrade log present (probably fresh insta

[Kernel-packages] [Bug 1748373] ProcModules.txt

2018-02-09 Thread John Smith
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051972/+files/ProcModules.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051976/+files/WifiSyslog.txt

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

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748373/+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 1748487] Missing required logs.

2018-02-09 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 1748487

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

Title:
  Please upgrade to get  kernel management

Status in acpi-support package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bionic still has that old version from 2013
  Debian have a more recent version: 
http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog
  Actual source: http://www.uefi.org/acpi

  Kernel (upstream) is supposed to have fixed the problem:
  
https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195

  Does ubuntu kernel apply that patch ?
  https://bugzilla.kernel.org/show_bug.cgi?id=117671

  Because kernel 4.15.0-9 still log these errors:

  kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170831/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170831/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20170831/tbxfload-246)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: acpi-support 0.142
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  9 17:49:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1748487/+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 1748244] Re: linux: 4.15.0-9.10 -proposed tracker

2018-02-09 Thread Brad Figg
** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Incomplete

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

Title:
  linux: 4.15.0-9.10 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1748244/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2018-02-09 Thread Peridot
I found it also boots with IOMMU turned on in the bios as long as you
set iommu=soft, both with the ubuntu kernel and the mainline kernel.

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/+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 1748373] RfKill.txt

2018-02-09 Thread John Smith
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1748373/+attachment/5051974/+files/RfKill.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051971/+files/ProcInterrupts.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051973/+files/PulseList.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748373/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2018-02-09 Thread Kai-Heng Feng
Is AMD-V enabled in BIOS?

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/+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 1748373] ProcCpuinfo.txt

2018-02-09 Thread John Smith
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051968/+files/ProcCpuinfo.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1748373/+attachment/5051966/+files/Lspci.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051963/+files/CurrentDmesg.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

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

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1748373/+attachment/5051975/+files/UdevDb.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051964/+files/IwConfig.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051970/+files/ProcEnviron.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/1748373

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1748373/+attachment/5051967/+files/Lsusb.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1748373/+attachment/5051962/+files/CRDA.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

2018-02-09 Thread John Smith
apport information

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

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748373/+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 1748373] Re: Resume from hibernate fails on latest kernels

2018-02-09 Thread John Smith
apport information

** Tags added: apport-collected artful

** Description changed:

  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but the
  three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32) fail:
  hibernate appears to succeed, but resume stops dead part-way through.
  This happens whether I use the built-in hibernate capability or usw-
  susp, and whether my Gnome session uses xorg or Wayland.
  
  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 
  
- Several other people have reported similar behaviour:
- https://ubuntuforums.org/showthread.php?t=2382336. (This report is an
- edited version of what I say there.)
+ Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  john   2636 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
+ InstallationDate: Installed on 2017-03-25 (321 days ago)
+ InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
+ MachineType: Dell Inc. Inspiron 15-3567
+ NonfreeKernelModules: wl
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-21-generic N/A
+  linux-backports-modules-4.13.0-21-generic  N/A
+  linux-firmware 1.169.3
+ Tags:  artful
+ Uname: Linux 4.13.0-21-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/12/2017
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 2.1.3
+ dmi.board.name: 0JVG7J
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 15-3567
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1748373/+attachment/5051961/+files/AlsaInfo.txt

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/s

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

2018-02-09 Thread Kleber Sacilotto de Souza
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1748486 (linux-aws), bug 1748488 (linux-lts-xenial)
+ derivatives: bug 1748489 (linux-aws), bug 1748490 (linux-euclid), bug 1748491 
(linux-gke), bug 1748492 (linux-kvm), bug 1748493 (linux-raspi2), bug 1748494 
(linux-snapdragon)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1748486 (linux-aws), bug 1748488 (linux-lts-xenial)
  derivatives: bug 1748489 (linux-aws), bug 1748490 (linux-euclid), bug 1748491 
(linux-gke), bug 1748492 (linux-kvm), bug 1748493 (linux-raspi2), bug 1748494 
(linux-snapdragon)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748484/+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 1748487] Re: Please upgrade to get kernel management

2018-02-09 Thread dino99
** Description changed:

  Bionic still has that old version from 2013
  Debian have a more recent version: 
http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog
+ Actual source: http://www.uefi.org/acpi
  
  Kernel (upstream) is supposed to have fixed the problem:
  
https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195
  
  Does ubuntu kernel apply that patch ?
  https://bugzilla.kernel.org/show_bug.cgi?id=117671
  
  Because kernel 4.15.0-9 still log these errors:
  
  kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170831/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170831/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20170831/tbxfload-246)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: acpi-support 0.142
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  9 17:49:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Please upgrade to get  kernel management

Status in acpi-support package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Bionic still has that old version from 2013
  Debian have a more recent version: 
http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog
  Actual source: http://www.uefi.org/acpi

  Kernel (upstream) is supposed to have fixed the problem:
  
https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195

  Does ubuntu kernel apply that patch ?
  https://bugzilla.kernel.org/show_bug.cgi?id=117671

  Because kernel 4.15.0-9 still log these errors:

  kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170831/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170831/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20170831/tbxfload-246)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: acpi-support 0.142
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  9 17:49:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1748487/+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 1748244] Re: linux: 4.15.0-9.10 -proposed tracker

2018-02-09 Thread Brad Figg
** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-development-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.15.0-9.10 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Friday, 09. February 2018 17:01 UTC

** Description changed:

  This bug is for tracking the 4.15.0-9.10 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Friday, 09. February 2018 17:01 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.15.0-9.10 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1748244/+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 1735271] Re: Update firmware for netronome SmartNICs

2018-02-09 Thread Seth Forshee
linux-firmware for bionic has been rebased onto upstream commit
2aa2ac2e9c09f09b0cfb6fc320c1e2d281530fa0 and now includes this merge.
Changing status to fix committed, I will be uploading a new linux-
firmware for bionic soon.

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

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

Title:
  Update firmware for netronome SmartNICs

Status in linux-firmware package in Ubuntu:
  Fix Committed

Bug description:
  Feature request for Bionic

  Update firmware for Netronome SmartNICs.
  It is planned to provide updated firmware to the linux-firmware project in 
the coming days
  and update this bug with the list of updated firmware accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1735271/+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 1748484] [NEW] linux: -proposed tracker

2018-02-09 Thread Kleber Sacilotto de Souza
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.02.01-2 kernel-sru-master-kernel xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importan

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

2018-02-09 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 1748373

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour:
  https://ubuntuforums.org/showthread.php?t=2382336. (This report is an
  edited version of what I say there.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748373/+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 1748487] [NEW] Please upgrade to get kernel management

2018-02-09 Thread dino99
Public bug reported:

Bionic still has that old version from 2013
Debian have a more recent version: 
http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog
Actual source: http://www.uefi.org/acpi

Kernel (upstream) is supposed to have fixed the problem:
https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195

Does ubuntu kernel apply that patch ?
https://bugzilla.kernel.org/show_bug.cgi?id=117671

Because kernel 4.15.0-9 still log these errors:

kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170831/dswload-210)
kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170831/tbxfload-228)
kernel: ACPI Error: 1 table load failures, 5 successful (20170831/tbxfload-246)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: acpi-support 0.142
ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
Uname: Linux 4.15.0-9-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Feb  9 17:49:39 2018
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: acpi-support
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: acpi-support (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug bionic upgrade-software-version

** Tags added: upgrade-software-version

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

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

Title:
  Please upgrade to get  kernel management

Status in acpi-support package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Bionic still has that old version from 2013
  Debian have a more recent version: 
http://metadata.ftp-master.debian.org/changelogs/main/a/acpi-support/acpi-support_0.142-8_changelog
  Actual source: http://www.uefi.org/acpi

  Kernel (upstream) is supposed to have fixed the problem:
  
https://github.com/torvalds/linux/blob/eceeae414edccb07fad683011c0c65abe8a3a554/include/acpi/acpixf.h#L195

  Does ubuntu kernel apply that patch ?
  https://bugzilla.kernel.org/show_bug.cgi?id=117671

  Because kernel 4.15.0-9 still log these errors:

  kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20170831/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20170831/psobject-252)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20170831/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20170831/tbxfload-246)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: acpi-support 0.142
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  9 17:49:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: acpi-support
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1748487/+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 1748486] [NEW] linux-aws: -proposed tracker

2018-02-09 Thread Kleber Sacilotto de Souza
Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1748484

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-aws (Ubuntu Trusty)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1748484 kernel-sru-cycle-2018.02.01-2 trusty

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: trusty

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: ker

[Kernel-packages] [Bug 1748489] [NEW] linux-aws: -proposed tracker

2018-02-09 Thread Kleber Sacilotto de Souza
Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1748484

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-aws (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.02.01-2 kernel-sru-derivative-of-1748484 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed

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

2018-02-09 Thread Kleber Sacilotto de Souza
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1748476 (linux-azure), bug 1748477 (linux-azure-edge), bug 
1748478 (linux-gcp), bug 1748479 (linux-hwe), bug 1748480 (linux-hwe-edge), bug 
1748481 (linux-oem)
+ derivatives: bug 1748483 (linux-raspi2)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

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

  backports: bug 1748476 (linux-azure), bug 1748477 (linux-azure-edge), bug 
1748478 (linux-gcp), bug 1748479 (linux-hwe), bug 1748480 (linux-hwe-edge), bug 
1748481 (linux-oem)
  derivatives: bug 1748483 (linux-raspi2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748475/+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 1748373] Re: Resume from hibernate fails on latest kernels

2018-02-09 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour:
  https://ubuntuforums.org/showthread.php?t=2382336. (This report is an
  edited version of what I say there.)

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

2018-02-09 Thread Kleber Sacilotto de Souza
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Status: Confirmed


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.02.01-2 kernel-sru-master-kernel

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: artful

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel T

[Kernel-packages] [Bug 1748373] [NEW] Resume from hibernate fails on latest kernels

2018-02-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but the
three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32) fail:
hibernate appears to succeed, but resume stops dead part-way through.
This happens whether I use the built-in hibernate capability or usw-
susp, and whether my Gnome session uses xorg or Wayland.

/var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted filesystem 
with ordered data mode. Opts: (null)
Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

Several other people have reported similar behaviour:
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an
edited version of what I say there.)

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


** Tags: bot-comment
-- 
Resume from hibernate fails on latest kernels
https://bugs.launchpad.net/bugs/1748373
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 1748470] Status changed to Confirmed

2018-02-09 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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2018-02-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

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

Bug description:
  Using artful kernel 4.12.0-13.14, Bluetooth audio works great.

  Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth
  audio issues which have manifested in a variety of weird ways:

  1) Playback would stall after 10-20 seconds
  2) Upon removing the device and attempting to redo pairing, no devices could 
be found to pair with
  3) After the device ended up reverting to low quality mono HSP mode, it could 
not be switched back to A2DP

  This is all rather vague - sorry - but it felt better to get notice of
  this regression into the bugtracker sooner rather than later.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maxb   2091 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 24 21:24:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
  InstallationDate: Installed on 2016-08-16 (404 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Spectre Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-31 (23 days ago)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81A0
  dmi.board.vendor: HP
  dmi.board.version: 48.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719210/+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 1746058] RfKill.txt

2018-02-09 Thread Cristian Aravena Romero
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1746058/+attachment/5051837/+files/RfKill.txt

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I'm checking:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/

  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [...]

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
* Kernel is compiled with IBRS/IBPB support:  YES 
* Currently enabled features
  * IBRS enabled for Kernel space:  NO 
  * IBRS enabled for User space:  NO 
  * IBPB enabled:  NO 
  * Mitigation 2
* Kernel compiled with retpoline option:  NO 
* Kernel compiled with a retpoline-aware compiler:  NO 
* Retpoline enabled:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  [...]

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1296 F pulseaudio
caravena   1698 F pulseaudio
  Date: Mon Jan 29 15:03:34 2018
  InstallationDate: Installed on 2017-10-13 (108 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-32-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-13 (118 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  Tags:  bionic
  Uname: Linux 4.15.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSA

[Kernel-packages] [Bug 1746058] UdevDb.txt

2018-02-09 Thread Cristian Aravena Romero
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1746058/+attachment/5051838/+files/UdevDb.txt

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I'm checking:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/

  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [...]

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
* Kernel is compiled with IBRS/IBPB support:  YES 
* Currently enabled features
  * IBRS enabled for Kernel space:  NO 
  * IBRS enabled for User space:  NO 
  * IBPB enabled:  NO 
  * Mitigation 2
* Kernel compiled with retpoline option:  NO 
* Kernel compiled with a retpoline-aware compiler:  NO 
* Retpoline enabled:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  [...]

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1296 F pulseaudio
caravena   1698 F pulseaudio
  Date: Mon Jan 29 15:03:34 2018
  InstallationDate: Installed on 2017-10-13 (108 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-32-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-13 (118 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  Tags:  bionic
  Uname: Linux 4.15.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSA

[Kernel-packages] [Bug 1746058] Re: CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

2018-02-09 Thread Cristian Aravena Romero
# ./spectre-meltdown-checker.sh 
Spectre and Meltdown mitigation detection tool v0.34+

Checking for vulnerabilities on current system
Kernel is Linux 4.15.0-9-generic #10-Ubuntu SMP Thu Feb 8 20:22:38 UTC 2018 
x86_64
CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)
* SPEC_CTRL MSR is available:  NO 
* CPU indicates IBRS capability:  NO 
  * Indirect Branch Prediction Barrier (IBPB)
* PRED_CMD MSR is available:  NO 
* CPU indicates IBPB capability:  NO 
  * Single Thread Indirect Branch Predictors (STIBP)
* SPEC_CTRL MSR is available:  NO 
* CPU indicates STIBP capability:  NO 
  * Enhanced IBRS (IBRS_ALL)
* CPU indicates ARCH_CAPABILITIES MSR availability:  NO 
* ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO 
  * CPU explicitly indicates not being vulnerable to Meltdown (RDCL_NO):  NO 
  * CPU microcode is known to cause stability problems:  NO  (model 42 stepping 
7 ucode 0x29)
* CPU vulnerability to the three speculative execution attacks variants
  * Vulnerable to Variant 1:  YES 
  * Vulnerable to Variant 2:  YES 
  * Vulnerable to Variant 3:  YES 

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Mitigated according to the /sys interface:  YES  (kernel confirms that the 
mitigation is active)
* Kernel has array_index_mask_nospec:  YES  (1 occurence(s) found of 64 bits 
array_index_mask_nospec())
> STATUS:  NOT VULNERABLE  (Mitigation: __user pointer sanitization)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Mitigated according to the /sys interface:  YES  (kernel confirms that the 
mitigation is active)
* Mitigation 1
  * Kernel is compiled with IBRS/IBPB support:  NO 
  * Currently enabled features
* IBRS enabled for Kernel space:  NO 
* IBRS enabled for User space:  NO 
* IBPB enabled:  NO 
* Mitigation 2
  * Kernel compiled with retpoline option:  YES 
  * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full 
retpoline compilation)
  * Retpoline enabled:  NO 
> STATUS:  NOT VULNERABLE  (Mitigation: Full generic retpoline)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Mitigated according to the /sys interface:  YES  (kernel confirms that the 
mitigation is active)
* Kernel supports Page Table Isolation (PTI):  YES 
* PTI enabled and active:  YES 
* Running as a Xen PV DomU:  NO 
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

A false sense of security is worse than no security at all, see
--disclaimer


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5753

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5754

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I'm checking:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/

  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [...]

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
* Kernel is compiled with IBRS/IBPB support:  YES 
* Currently enabled features
  * IBRS enabled for Kernel space:  NO 
  * IBRS enabled for User space:  NO 
  * IBPB enabled:  NO 
  * Mitigation 2
* Kernel compiled with retpoline option:  NO 
* Kernel compiled with a retpoline-aware compiler:  NO 
* Retpoline enabled:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  [...]

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1296 F pulseaudio
caravena   1698 F pulseaudio
  Date: Mon Jan 29 15:03:34 2018
  InstallationDate: Installed on 2017-10-13 (108 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-32-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-gener

[Kernel-packages] [Bug 1746058] WifiSyslog.txt

2018-02-09 Thread Cristian Aravena Romero
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1746058/+attachment/5051839/+files/WifiSyslog.txt

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I'm checking:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/

  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [...]

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
* Kernel is compiled with IBRS/IBPB support:  YES 
* Currently enabled features
  * IBRS enabled for Kernel space:  NO 
  * IBRS enabled for User space:  NO 
  * IBPB enabled:  NO 
  * Mitigation 2
* Kernel compiled with retpoline option:  NO 
* Kernel compiled with a retpoline-aware compiler:  NO 
* Retpoline enabled:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  [...]

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1296 F pulseaudio
caravena   1698 F pulseaudio
  Date: Mon Jan 29 15:03:34 2018
  InstallationDate: Installed on 2017-10-13 (108 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-32-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-13 (118 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  Tags:  bionic
  Uname: Linux 4.15.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr

  1   2   >