[Kernel-packages] [Bug 1746936] Re: linux: 4.4.0-113.136 -proposed tracker

[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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** 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: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 08. February 2018 07:33 UTC

** 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: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 08. February 2018 07:33 UTC
+ 
+ -- swm properties --
+ boot-testing-requested: true
+ 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/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:
  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:
  Confirmed
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: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 08. February 2018 07:33 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[ChristianEhrhardt]

FYI: The discussion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889010 
nicely outlined that we rely on those hooks in chrony.
That makes having them working critical for 18.04 to have it working correctly 
for late or changing network topology.

We (cyphermox and me) discussed how I could convert the chrony hooks but found 
not clear solution. It ended in the app needing to listen for netlink events, 
but we can't/won't do that for all the affected packages.
That said implementing sort of a generic solution a package can plug into gets 
more and more important.

** Bug watch added: Debian Bug tracker #889010
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889010

** Changed in: chrony (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: chrony (Ubuntu)
Milestone: None => ubuntu-18.03

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Committed
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New
Status in vzctl package in Ubuntu:
  New
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   

[Kernel-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Kai-Heng Feng]

Please attach dmesg under v4.15.1, thanks!

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

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

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

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

  The previous answers listed below suggest the following diagnostics

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

  The service seems to be running

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

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

  and not blocked

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

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

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

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

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

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

  and the output of dmsg is

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

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Thanking you in anticipation
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: 

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

[Kai-Heng Feng]

https://lkml.org/lkml/2018/2/8/19

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

[Kai-Heng Feng]

https://lkml.org/lkml/2018/2/8/5

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164/+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 1746848] Re: Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15 retina 2013 late

[Kai-Heng Feng]

Please attach "/sys/kernel/debug/wakeup_sources" before and after it
auto woke up. We can see which device woke the machine up.

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

Title:
  Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15
  retina 2013 late

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I click on the suspend button (alternative of power off button)
  in the menu or I click the power button, the Ubuntu seems like will be
  suspended (with a black screen) and, after 5-10 seconds, come back to
  the login screen.

  Closing the lid also doesn't take effect. It doesn't even turn off the
  display.

  I found that clicking on the suspend button and very quickly closing
  the lid seems to make it stays suspended.

  I'm having this trouble in a Macbook Pro 15 retina 2013 late running a
  Ubuntu 17.10 in the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otto   1600 F pulseaudio
   /dev/snd/controlC0:  otto   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 22:58:16 2018
  InstallationDate: Installed on 2018-01-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00F2.B00.1708080809
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00F2.B00.1708080809:bd08/08/2017:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro10,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/1746848/+subscriptions

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

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

[Kai-Heng Feng]

> On Feb 8, 2018, at 10:19 AM, Lucas Zanella <1746...@bugs.launchpad.net> wrote:
> 
> I added an USB wireless receiver to use internet to download things so I
> can see if something happens. I installed more system updates through
> the ubuntu software updates. Is this ok? The kernel will still be yours,
> rigtht?

I should be. You can use `uname -r` to check the kernel version.

> 
> -- 
> You received this bug notification because you are 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
>   

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

[Kai-Heng Feng]

> On Feb 8, 2018, at 5:16 AM, Mehdinefrance <1655...@bugs.launchpad.net> wrote:
> 
> Thanks for your message Kai-Heng Feng.
> 
> I am puzzled when I click on the link you sent me, even after having
> checked the help section
> (https://wiki.ubuntu.com/Kernel/MainlineBuilds).
> 
> Is there any possibility for me to make a live-usb key with a mainline
> kernel so that I can test it on my computer ? If so, is there any iso
> image I could download ?

No. not really. I guess install these packages directly on your machine
is a better way to do it.

> 
> -- 
> You received this bug notification because you are 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

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

[Kernel-packages] [Bug 1748075] Re: linux: 4.15.0-8.9 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.15.0-8.9 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
+ 
+ kernel-phase-changed:Thursday, 08. February 2018 03:32 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.15.0-8.9 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
  
  kernel-phase-changed:Thursday, 08. February 2018 03:32 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.15.0-8.9 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
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-8.9 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

  kernel-phase-changed:Thursday, 08. February 2018 03:32 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1748075/+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 1742675] Re: after upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all

[Dmitriy Merzlov]

Upgrading to kernel 4.13.0-33.36 from ppa:canonical-kernel-team/ppa solved the 
issue. 
No need to use "acpi=off"

System works stable. (Dell E5570 i5-6300U Skylake)

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

Title:
  after upgrade to linux-image-extra-4.13.0-26-generic  the system does
  not start at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to linux-image-extra-4.13.0-26-generic  the system does not 
start at all.
  Only restart through Advanced Options with 
linux-image-extra-4.10.0-42-generic helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jan 11 15:20:26 2018
  InstallationDate: Installed on 2017-06-23 (201 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2017-06-24T18:05:02.372991

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+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 1748072] [NEW] Bionic update to v4.15.2 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.15.2 stable release shall be
applied:

KVM: x86: Make indirect calls in emulator speculation safe
KVM: VMX: Make indirect call speculation safe
module/retpoline: Warn about missing retpoline in module
x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
x86/cpufeatures: Add Intel feature bits for Speculation Control
x86/cpufeatures: Add AMD feature bits for Speculation Control
x86/msr: Add definitions for new speculation control MSRs
x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown
x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early Spectre v2 microcodes
x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support
x86/alternative: Print unadorned pointers
x86/nospec: Fix header guards names
x86/bugs: Drop one "mitigation" from dmesg
x86/cpu/bugs: Make retpoline module warning conditional
x86/cpufeatures: Clean up Spectre v2 related CPUID flags
x86/retpoline: Simplify vmexit_fill_RSB()
x86/speculation: Simplify indirect_branch_prediction_barrier()
auxdisplay: img-ascii-lcd: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
iio: adc/accel: Fix up module licenses
pinctrl: pxa: pxa2xx: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
ASoC: pcm512x: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
KVM: nVMX: Eliminate vmcs02 pool
KVM: VMX: introduce alloc_loaded_vmcs
objtool: Improve retpoline alternative handling
objtool: Add support for alternatives at the end of a section
objtool: Warn on stripped section symbol
x86/mm: Fix overlap of i386 CPU_ENTRY_AREA with FIX_BTMAP
x86/spectre: Check CONFIG_RETPOLINE in command line parser
x86/entry/64: Remove the SYSCALL64 fast path
x86/entry/64: Push extra regs right away
x86/asm: Move 'status' from thread_struct to thread_info
Documentation: Document array_index_nospec
array_index_nospec: Sanitize speculative array de-references
x86: Implement array_index_mask_nospec
x86: Introduce barrier_nospec
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/get_user: Use pointer masking to limit speculation
x86/syscall: Sanitize syscall table de-references under speculation
vfs, fdtable: Prevent bounds-check bypass via speculative execution
nl80211: Sanitize array index in parse_txq_params
x86/spectre: Report get_user mitigation for spectre_v1
x86/spectre: Fix spelling mistake: "vunerable"-> "vulnerable"
x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel
x86/speculation: Use Indirect Branch Prediction Barrier in context switch
x86/paravirt: Remove 'noreplace-paravirt' cmdline option
KVM: VMX: make MSR bitmaps per-VCPU
x86/kvm: Update spectre-v1 mitigation
x86/retpoline: Avoid retpolines for built-in __init functions
x86/spectre: Simplify spectre_v2 command line parsing
x86/pti: Mark constant arrays as __initconst
x86/speculation: Fix typo IBRS_ATT, which should be IBRS_ALL
KVM/x86: Update the reverse_cpuid list to include CPUID_7_EDX
KVM/x86: Add IBPB support
KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
serial: core: mark port as initialized after successful IRQ change
fpga: region: release of_parse_phandle nodes after use
Linux 4.15.2

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.15.2 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported 

[Kernel-packages] [Bug 1748070] [NEW] Bionic update to v4.14.18 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.14.18 stable release shall be
applied:

scripts/faddr2line: fix CROSS_COMPILE unset error
powerpc/64s: Wire up cpu_show_meltdown()
powerpc/64s: Allow control of RFI flush via debugfs
x86/retpoline: Remove the esp/rsp thunk
KVM: x86: Make indirect calls in emulator speculation safe
KVM: VMX: Make indirect call speculation safe
module/retpoline: Warn about missing retpoline in module
x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
x86/cpufeatures: Add Intel feature bits for Speculation Control
x86/cpufeatures: Add AMD feature bits for Speculation Control
x86/msr: Add definitions for new speculation control MSRs
x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown
x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early Spectre v2 microcodes
x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support
x86/alternative: Print unadorned pointers
x86/nospec: Fix header guards names
x86/bugs: Drop one "mitigation" from dmesg
x86/cpu/bugs: Make retpoline module warning conditional
x86/cpufeatures: Clean up Spectre v2 related CPUID flags
x86/retpoline: Simplify vmexit_fill_RSB()
x86/speculation: Simplify indirect_branch_prediction_barrier()
auxdisplay: img-ascii-lcd: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
iio: adc/accel: Fix up module licenses
pinctrl: pxa: pxa2xx: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
ASoC: pcm512x: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
KVM: nVMX: Eliminate vmcs02 pool
KVM: VMX: introduce alloc_loaded_vmcs
objtool: Improve retpoline alternative handling
objtool: Add support for alternatives at the end of a section
objtool: Warn on stripped section symbol
x86/mm: Fix overlap of i386 CPU_ENTRY_AREA with FIX_BTMAP
x86/spectre: Check CONFIG_RETPOLINE in command line parser
x86/entry/64: Remove the SYSCALL64 fast path
x86/entry/64: Push extra regs right away
x86/asm: Move 'status' from thread_struct to thread_info
Documentation: Document array_index_nospec
array_index_nospec: Sanitize speculative array de-references
x86: Implement array_index_mask_nospec
x86: Introduce barrier_nospec
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/get_user: Use pointer masking to limit speculation
x86/syscall: Sanitize syscall table de-references under speculation
vfs, fdtable: Prevent bounds-check bypass via speculative execution
nl80211: Sanitize array index in parse_txq_params
x86/spectre: Report get_user mitigation for spectre_v1
x86/spectre: Fix spelling mistake: "vunerable"-> "vulnerable"
x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel
x86/speculation: Use Indirect Branch Prediction Barrier in context switch
x86/paravirt: Remove 'noreplace-paravirt' cmdline option
KVM: VMX: make MSR bitmaps per-VCPU
x86/kvm: Update spectre-v1 mitigation
x86/retpoline: Avoid retpolines for built-in __init functions
x86/spectre: Simplify spectre_v2 command line parsing
x86/pti: Mark constant arrays as __initconst
x86/speculation: Fix typo IBRS_ATT, which should be IBRS_ALL
KVM/x86: Update the reverse_cpuid list to include CPUID_7_EDX
KVM/x86: Add IBPB support
KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
serial: core: mark port as initialized after successful IRQ change
fpga: region: release of_parse_phandle nodes after use
Linux 4.14.18

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.14.18 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has 

[Kernel-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

[naisanza]

And also:

'dpkg-query: no packages found matching linux'

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1734728] Re: linux: 4.14.0-9.11 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-9.11 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-9.11 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

  kernel-phase:Packaging
  kernel-phase-changed:Monday, 27. November 2017 18:00 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1734728/+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 1741139] Re: linux: 4.14.0-14.17 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-14.17 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
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:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-14.17 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1741139/+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 1734901] Re: linux: 4.14.0-10.12 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-10.12 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-10.12 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

  kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1734901/+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 1736168] Re: linux: 4.14.0-11.13 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
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.14.0-11.13 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/1736168/+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 1734695] Re: linux: 4.14.0-8.10 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-8.10 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-8.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

  kernel-phase:Packaging
  kernel-phase-changed:Monday, 27. November 2017 14:00 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1734695/+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 1738554] Re: linux: 4.14.0-12.14 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-12.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-12.14 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

  kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1738554/+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 1741501] Re: linux: 4.14.0-15.18 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-15.18 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
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:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-15.18 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1741501/+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 1738848] Re: linux: 4.14.0-13.15 -proposed tracker

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-13.15 -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.14.0-13.15 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/1738848/+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 1748070] Re: Bionic update to v4.14.18 stable release

[Seth Forshee]

** Changed in: linux (Ubuntu)
   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/1748070

Title:
  Bionic update to v4.14.18 stable release

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.14.18 stable release shall be
  applied:

  scripts/faddr2line: fix CROSS_COMPILE unset error
  powerpc/64s: Wire up cpu_show_meltdown()
  powerpc/64s: Allow control of RFI flush via debugfs
  x86/retpoline: Remove the esp/rsp thunk
  KVM: x86: Make indirect calls in emulator speculation safe
  KVM: VMX: Make indirect call speculation safe
  module/retpoline: Warn about missing retpoline in module
  x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
  x86/cpufeatures: Add Intel feature bits for Speculation Control
  x86/cpufeatures: Add AMD feature bits for Speculation Control
  x86/msr: Add definitions for new speculation control MSRs
  x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown
  x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early Spectre v2 microcodes
  x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support
  x86/alternative: Print unadorned pointers
  x86/nospec: Fix header guards names
  x86/bugs: Drop one "mitigation" from dmesg
  x86/cpu/bugs: Make retpoline module warning conditional
  x86/cpufeatures: Clean up Spectre v2 related CPUID flags
  x86/retpoline: Simplify vmexit_fill_RSB()
  x86/speculation: Simplify indirect_branch_prediction_barrier()
  auxdisplay: img-ascii-lcd: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
  iio: adc/accel: Fix up module licenses
  pinctrl: pxa: pxa2xx: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
  ASoC: pcm512x: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE
  KVM: nVMX: Eliminate vmcs02 pool
  KVM: VMX: introduce alloc_loaded_vmcs
  objtool: Improve retpoline alternative handling
  objtool: Add support for alternatives at the end of a section
  objtool: Warn on stripped section symbol
  x86/mm: Fix overlap of i386 CPU_ENTRY_AREA with FIX_BTMAP
  x86/spectre: Check CONFIG_RETPOLINE in command line parser
  x86/entry/64: Remove the SYSCALL64 fast path
  x86/entry/64: Push extra regs right away
  x86/asm: Move 'status' from thread_struct to thread_info
  Documentation: Document array_index_nospec
  array_index_nospec: Sanitize speculative array de-references
  x86: Implement array_index_mask_nospec
  x86: Introduce barrier_nospec
  x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
  x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
  x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
  x86/get_user: Use pointer masking to limit speculation
  x86/syscall: Sanitize syscall table de-references under speculation
  vfs, fdtable: Prevent bounds-check bypass via speculative execution
  nl80211: Sanitize array index in parse_txq_params
  x86/spectre: Report get_user mitigation for spectre_v1
  x86/spectre: Fix spelling mistake: "vunerable"-> "vulnerable"
  x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel
  x86/speculation: Use Indirect Branch Prediction Barrier in context switch
  x86/paravirt: Remove 'noreplace-paravirt' cmdline option
  KVM: VMX: make MSR bitmaps per-VCPU
  x86/kvm: Update spectre-v1 mitigation
  x86/retpoline: Avoid retpolines for built-in __init functions
  x86/spectre: Simplify spectre_v2 command line parsing
  x86/pti: Mark constant arrays as __initconst
  x86/speculation: Fix typo IBRS_ATT, which should be IBRS_ALL
  KVM/x86: Update the reverse_cpuid list to include CPUID_7_EDX
  KVM/x86: Add IBPB support
  KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
  KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL
  KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL
  serial: core: mark port as initialized after successful IRQ change
  fpga: region: release of_parse_phandle nodes after use
  Linux 4.14.18

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

[Seth Forshee]

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

** This bug is no longer a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker
** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-16.19 -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 Committed
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.14.0-16.19 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1741920/+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 1748075] [NEW] linux: 4.15.0-8.9 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 4.15.0-8.9 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-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: bionic

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu)
   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/1748075

Title:
  linux: 4.15.0-8.9 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in 

[Kernel-packages] [Bug 1744981] Re: linux: 4.14.0-17.20 -proposed tracker

[Seth Forshee]

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

** This bug has been marked a duplicate of bug 1748075
   linux: 4.15.0-8.9 -proposed tracker

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

Title:
  linux: 4.14.0-17.20 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-17.20 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

  kernel-phase:Packaging
  kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1744981/+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 1747488] ProcCpuinfo.txt

[naisanza]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051030/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

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

[naisanza]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051031/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

[naisanza]

Looks like mesa isn't installed

'dpkg-query: no packages found matching mesa'

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1747488] WifiSyslog.txt

[naisanza]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051036/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post 

[Kernel-packages] [Bug 1747488] ProcInterrupts.txt

[naisanza]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051032/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: 

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

[naisanza]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051033/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1747488] UdevDb.txt

[naisanza]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1747488/+attachment/5051035/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1747488] PulseList.txt

[naisanza]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051034/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to 

[Kernel-packages] [Bug 1747488] Lspci.txt

[naisanza]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1747488/+attachment/5051028/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1747488] Lsusb.txt

[naisanza]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1747488/+attachment/5051029/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1747488] JournalErrors.txt

[naisanza]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051027/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1747488] DpkgLog.txt

[naisanza]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051024/+files/DpkgLog.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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to 

[Kernel-packages] [Bug 1747488] CurrentDmesg.txt

[naisanza]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051023/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1747488] IwConfig.txt

[naisanza]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051026/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to   

[Kernel-packages] [Bug 1747488] HookError_source_mesa.txt

[naisanza]

apport information

** Attachment added: "HookError_source_mesa.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051025/+files/HookError_source_mesa.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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1747488] CRDA.txt

[naisanza]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1747488/+attachment/5051022/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  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.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

[naisanza]

apport information

** Tags added: ubuntu

** Description changed:

  Ubuntu 17.10.1 boots into a black screen with no display, when switching
  into "EFI VGA" during boot up.
  
  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:
  
  "Switching to EFI VGA"
  
  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works
  
  PC Specs
  
  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  eric   2029 F pulseaudio
+  /dev/snd/controlC1:  eric   2029 F pulseaudio
+  /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
+  /dev/snd/controlC0:  eric   2029 F pulseaudio
+ CurrentDesktop: GNOME
+ DistUpgraded: Fresh install
+ DistroCodename: artful
+ DistroRelease: Ubuntu 17.10
+ DistroVariant: ubuntu
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
+ InstallationDate: Installed on 2018-02-05 (2 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: mesa (not installed)
+ ProcEnviron:
+  TERM=screen
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
+ 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.169.3
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: yes
+ Tags:  artful ubuntu
+ 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: 08/08/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P1.60
+ dmi.board.name: X299 Taichi
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.family: To Be Filled By O.E.M.
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.83-1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
+ version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
+ version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1747488/+attachment/5051021/+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/1747488

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot 

[Kernel-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

[Daniel van Vugt]

Thanks. Problems specific to nouveau like this are either going to be in
the mesa package, or the kernel. Maybe 'mutter' but that's less likely.

** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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

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

[Ubuntu Kernel Bot]

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

apport-collect 1747488

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747488/+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 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

[Daniel van Vugt]

** Also affects: libinput via
   https://bugs.freedesktop.org/show_bug.cgi?id=104990
   Importance: Unknown
   Status: Unknown

** Changed in: libinput (Ubuntu)
   Status: Incomplete => 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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Unknown
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

[Lucas Zanella]

I added an USB wireless receiver to use internet to download things so I
can see if something happens. I installed more system updates through
the ubuntu software updates. Is this ok? The kernel will still be yours,
rigtht?

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

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

[Lucas Zanella]

After installing everything, I rebooted to use the new kernel. I then
installed updates on the machine to see if the problem would happen
(easier way to make it happen is on the moment I try to update). After
the update, wireless stopped working. Restarted many times and still not
working.

Could it be that the update triggered the error and the so called pcie
reset of this kernel made the wireless go wrong?

I'm gonna still use this kernel to see if the read only filesystem
happens 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
   

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

[Lucas Zanella]

I downloaded again and it seems that this time it wasn't corrupted.

Output:

Preparing to unpack linux-headers-4.15.0+_4.15.0+-2_amd64.deb ...
Unpacking linux-headers-4.15.0+ (4.15.0+-2) over (4.15.0+-2) ...
Preparing to unpack linux-image-4.15.0+_4.15.0+-2_amd64(1).deb ...
Unpacking linux-image-4.15.0+ (4.15.0+-2) over (4.15.0+-2) ...
Preparing to unpack linux-image-4.15.0+-dbg_4.15.0+-2_amd64(1).deb ...
Unpacking linux-image-4.15.0+-dbg (4.15.0+-2) ...
Preparing to unpack linux-libc-dev_4.15.0+-2_amd64.deb ...
Unpacking linux-libc-dev (4.15.0+-2) over (4.15.0+-2) ...
Setting up linux-headers-4.15.0+ (4.15.0+-2) ...
Setting up linux-image-4.15.0+ (4.15.0+-2) ...
update-initramfs: Generating /boot/initrd.img-4.15.0+
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_39.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver9_29.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module 
i915
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.15.0+
Found initrd image: /boot/initrd.img-4.15.0+
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-4.15.0+-dbg (4.15.0+-2) ...
Setting up linux-libc-dev (4.15.0+-2) ...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 

[Kernel-packages] [Bug 1746848] Re: Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15 retina 2013 late

[Otto Julio Ahlert Pinno]

Hi Joseph,

I did a fresh install of Ubuntu 17.10 and was not using the Linux before
on this machine, so I cannot tell if there is some prior kernel that
doesn't have the problem. But I think it is an old problem:

https://askubuntu.com/questions/158532/xubuntu-12-04-restarts-after-
suspend-only-from-my-account

I already tried to move ~/.config directory and create a new user as
described as a workaround in the link above, but haven't had success.

I tested with the mainline Kernel v4.15.1. With this kernel the screen
keeps turned off and the USB devices seems to be turned off also.
However, the cooler keeps blowing a hot air. Furthermore, closing the
lid seems to have no effect. With kernel v4.13.0-32, the cooler stops
completely but it returns to the login screen as described in the bug
description.

I attached the dmesg generated from a suspension try (kernel
v4.13.0-32). Maybe, its information helps. A partial quote of it:

...
[   58.300375] ACPI: Preparing to enter system sleep state S3
[   58.364061] ACPI: EC: event blocked
[   58.364062] ACPI: EC: EC stopped
[   58.364062] PM: Saving platform NVS memory
[   58.364066] Disabling non-boot CPUs ...
[   58.381470] smpboot: CPU 1 is now offline
[   58.409535] smpboot: CPU 2 is now offline
[   58.437577] smpboot: CPU 3 is now offline
[   58.460542] IRQ 31: no longer affine to CPU4
[   58.462090] smpboot: CPU 4 is now offline
[   58.484496] IRQ 30: no longer affine to CPU5
[   58.484507] IRQ 50: no longer affine to CPU5
[   58.485520] smpboot: CPU 5 is now offline
[   58.508488] IRQ 23: no longer affine to CPU6
[   58.508493] IRQ 28: no longer affine to CPU6
[   58.508495] IRQ 29: no longer affine to CPU6
[   58.509517] smpboot: CPU 6 is now offline
[   58.532450] IRQ 8: no longer affine to CPU7
[   58.532453] IRQ 9: no longer affine to CPU7
[   58.532462] IRQ 17: no longer affine to CPU7
[   58.532467] IRQ 22: no longer affine to CPU7
[   58.533500] smpboot: CPU 7 is now offline
[   58.535303] ACPI: Low-level resume complete
[   58.535353] ACPI: EC: EC started
...

Thank you for your time.

** Attachment added: "dmesg of a suspension try - kernel v4.13.0-32"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746848/+attachment/5051008/+files/dmesg.txt

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15
  retina 2013 late

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I click on the suspend button (alternative of power off button)
  in the menu or I click the power button, the Ubuntu seems like will be
  suspended (with a black screen) and, after 5-10 seconds, come back to
  the login screen.

  Closing the lid also doesn't take effect. It doesn't even turn off the
  display.

  I found that clicking on the suspend button and very quickly closing
  the lid seems to make it stays suspended.

  I'm having this trouble in a Macbook Pro 15 retina 2013 late running a
  Ubuntu 17.10 in the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otto   1600 F pulseaudio
   /dev/snd/controlC0:  otto   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 22:58:16 2018
  InstallationDate: Installed on 2018-01-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00F2.B00.1708080809
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00F2.B00.1708080809:bd08/08/2017:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.family: Mac
  

[Kernel-packages] [Bug 1734457] Re: Xorg freeze

[Christopher M. Penalver]

Torsten Schönfeld, thank you for reporting this and helping make Ubuntu
better.

In order to allow additional upstream mainline kernel developers to examine the 
issue, at your earliest convenience, could you please test the latest mainline 
kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? 
Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the report 
description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

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

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

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

** Summary changed:

- Xorg freeze
+ kernel crash

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

Title:
  kernel crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been experiencing this freeze ever since I got the Sapphire
  Nitro+ RX 470 8GB.  It happens fairly quickly when watching web video,
  but occasionally also when using Thunderbird or Firefox normally.

  Call trace from the last freeze:

  Nov 25 17:46:20 home.hcsiteeffak.de kernel: INFO: task amdgpu_cs:0:2905 
blocked for more than 120 seconds.
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:   Not tainted 
4.13.0-17-generic #20-Ubuntu
  Nov 25 17:46:20 home.hcsiteeffak.de kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Nov 25 17:46:20 home.hcsiteeffak.de kernel: amdgpu_cs:0 D0  2905   
2902 0x
  Nov 25 17:46:20 home.hcsiteeffak.de kernel: Call Trace:
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  __schedule+0x28b/0x890
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  schedule+0x36/0x80
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  
amd_sched_entity_push_job+0xc5/0x110 [amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? wait_woken+0x80/0x80
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_job_submit+0x73/0x90 
[amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  
amdgpu_vm_bo_update_mapping+0x3b0/0x400 [amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? 
amdgpu_vm_validate_level.isra.11+0x90/0x90 [amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_vm_clear_freed+0x90/0x140 
[amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_gem_va_ioctl+0x49b/0x4e0 
[amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? kvfree+0x33/0x40
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  drm_ioctl_kernel+0x5d/0xb0 [drm]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? drm_ioctl_kernel+0x5d/0xb0 
[drm]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  drm_ioctl+0x31b/0x3d0 [drm]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? futex_wake+0x8f/0x180
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_drm_ioctl+0x4f/0x90 
[amdgpu]
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  do_vfs_ioctl+0xa5/0x610
  Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? SyS_futex+0x13b/0x180
  Nov 25 17:46:20 

[Kernel-packages] [Bug 1734457] [NEW] Xorg freeze

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I've been experiencing this freeze ever since I got the Sapphire Nitro+
RX 470 8GB.  It happens fairly quickly when watching web video, but
occasionally also when using Thunderbird or Firefox normally.

Call trace from the last freeze:

Nov 25 17:46:20 home.hcsiteeffak.de kernel: INFO: task amdgpu_cs:0:2905 blocked 
for more than 120 seconds.
Nov 25 17:46:20 home.hcsiteeffak.de kernel:   Not tainted 4.13.0-17-generic 
#20-Ubuntu
Nov 25 17:46:20 home.hcsiteeffak.de kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 25 17:46:20 home.hcsiteeffak.de kernel: amdgpu_cs:0 D0  2905   2902 
0x
Nov 25 17:46:20 home.hcsiteeffak.de kernel: Call Trace:
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  __schedule+0x28b/0x890
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  schedule+0x36/0x80
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  
amd_sched_entity_push_job+0xc5/0x110 [amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? wait_woken+0x80/0x80
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_job_submit+0x73/0x90 
[amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  
amdgpu_vm_bo_update_mapping+0x3b0/0x400 [amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? 
amdgpu_vm_validate_level.isra.11+0x90/0x90 [amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_vm_clear_freed+0x90/0x140 
[amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_gem_va_ioctl+0x49b/0x4e0 
[amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? kvfree+0x33/0x40
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  drm_ioctl_kernel+0x5d/0xb0 [drm]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? drm_ioctl_kernel+0x5d/0xb0 [drm]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  drm_ioctl+0x31b/0x3d0 [drm]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? 
amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? futex_wake+0x8f/0x180
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  amdgpu_drm_ioctl+0x4f/0x90 [amdgpu]
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  do_vfs_ioctl+0xa5/0x610
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  ? SyS_futex+0x13b/0x180
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  SyS_ioctl+0x79/0x90
Nov 25 17:46:20 home.hcsiteeffak.de kernel:  entry_SYSCALL_64_fastpath+0x1e/0xa9
Nov 25 17:46:20 home.hcsiteeffak.de kernel: RIP: 0033:0x7ffb136e4ea7
Nov 25 17:46:20 home.hcsiteeffak.de kernel: RSP: 002b:7ffb089919b8 EFLAGS: 
0246 ORIG_RAX: 0010
Nov 25 17:46:20 home.hcsiteeffak.de kernel: RAX: ffda RBX: 
564219d52c10 RCX: 7ffb136e4ea7
Nov 25 17:46:20 home.hcsiteeffak.de kernel: RDX: 7ffb08991a00 RSI: 
c0286448 RDI: 000e
Nov 25 17:46:20 home.hcsiteeffak.de kernel: RBP: 7ffb08991a90 R08: 
00010ff8 R09: 000e
Nov 25 17:46:20 home.hcsiteeffak.de kernel: R10: 002f R11: 
0246 R12: c0186444
Nov 25 17:46:20 home.hcsiteeffak.de kernel: R13: 000e R14: 
 R15: 564219d4e320

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Nov 25 17:59:47 2017
DistUpgraded: 2017-09-26 19:40:21,084 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Once a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev cf) (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 
[174b:e347]
InstallationDate: Installed on 2013-06-01 (1637 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=f06ea0dd-7dd8-44a5-9bd2-75559dc31d93 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to artful on 2017-09-26 (59 days ago)
dmi.bios.date: 01/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1305
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-PRO
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: 

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Joseph Salisbury]

Yes, the SRU request noted in comment #7 is for Xenial and 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/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:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  In Progress
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 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

[Stephen A. Zarkos]

FYI, we are looking for this in the default Xenial kernel as well.
There are some bare metal systems in use that wouldn't be able to use
the Azure 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/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:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  In Progress
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 1746946] Re: linux-aws: 4.4.0-1051.60 -proposed tracker

[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

** 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: 1746936
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 08. February 2018 00:21 UTC

** 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 --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1746936
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 08. February 2018 00:21 UTC
+ phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1051.60 -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 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:
  Invalid
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1746936
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746946/+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

[Paul Friel]

@kamalmostafa: Do you all have a target date for when the new linux-aws
kernel (4.4.0-1051.60) will be released?

Thanks everyone for your help in quickly tracking down this issue.

-- 
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 1747902] Re: System does not resume after hibernate

[David Emmett]

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

** This bug has been marked a duplicate of bug 1743094
   [regression] hibernation (freezes on resume) since 4.13.0-25.29

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

Title:
  System does not resume after hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the update from linux-4.13.0-21-generic to
  linux-4.13.0-25-generic, resuming after hibernation no longer works.
  The problem persists after updates to 4.13.0-31-generic and
  4.13.0-32-generic.

  The system goes into hibernation correctly, shutting down properly
  when the power button is pressed (configured to hibernate system). But
  when the power button is pressed again (or the laptop lid opened), the
  system gets passed the grub menu and then hangs.

  On 4.13.0-21-generic, where hibernation works, the splash screen
  briefly displays a message about loading an img and then boots.

  From 4.13.0-25-generic, the system never reaches this stage. Nothing
  is ever logged in kernel.log or by dmesg, and the system hangs with a
  blank screen. The system is unresponsive to any input. I have to press
  and hold the power button, after which the system reboots as if from a
  fresh boot.

  Desired behavior is obviously that the system resumes after
  hibernation and restores itself to its previous state. Hibernation
  works perfectly on 4.13.0-21-generic, but not since then.

  I have attached the output from 4.13.0-21-generic and
  4.13.0-32-generic of the following for comparison

  $ uname -a > uname-a.log
  $ cat /proc/version_signature > version.log
  $ dmesg > dmesg.log
  $ sudo lspci -vvnn > lspci-vvnn.log

  My system is a Lenovo Thinkpad T460 with 16GB of RAM, and a 512GB SSD.
  I have 14.9GB of swap. The behavior is identical regardless of whether
  I have external screens, mice, keyboards, etc attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1982 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Feb  7 13:03:27 2018
  HibernationDevice: RESUME=UUID=3f54853d-1d7f-426b-9cfd-22ce1f6a1dc7
  InstallationDate: Installed on 2016-12-29 (404 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FNCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=70437d43-e174-4edf-97f8-613c1cb99b22 ro quiet splash 
UUID=3f54853d-1d7f-426b-9cfd-22ce1f6a1dc7 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-24 (106 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET58W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET58W(1.32):bd12/15/2017:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FNCTO1WW
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747902/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

[Krystian Maculewicz]

Sorry not fixed, was mislead by strange behavior. 
If i will reboot from latest working kernel .21 to 4.13.0-33.36, resume from 
hibernation fail with logs:
[3.101197] PM: Using 3 thread(s) for decompression.
   PM: Loading and decompressing image data (510246 pages)...
[3.101206] Hibernate inconsistent memory map detected!
[3.101207] PM: Image mismatch: architecture specific data
[3.101209] PM: Read 2040984 kbytes in 0.01 seconds (204098.40 MB/s)
[3.101748] PM: Error -1 resuming
[3.101750] PM: Failed to load hibernation image, recovering.
[3.102068] PM: Basic memory bitmaps freed

-- 
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 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[John Lenton]

Hello,

I tried with

$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342DESIGNWAREConfigsV2 SMP Wed Feb 7 
20:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

and the bug is still there.

Sorry...

-- 
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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

[Krystian Maculewicz]

Working in latest 4.13.0-33.36 from artful-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/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)

[Lucas Zanella]

Thanks. What's a 'PCI reset for NVMe device after resume'?

Here's the output of running sudo dpkg -i *.deb on the 4 files:

Selecting previously unselected package linux-headers-4.15.0+.
(Reading database ... 137951 files and directories currently installed.)
Preparing to unpack linux-headers-4.15.0+_4.15.0+-2_amd64.deb ...
Unpacking linux-headers-4.15.0+ (4.15.0+-2) ...
Selecting previously unselected package linux-image-4.15.0+.
Preparing to unpack linux-image-4.15.0+_4.15.0+-2_amd64.deb ...
Unpacking linux-image-4.15.0+ (4.15.0+-2) ...
Selecting previously unselected package linux-image-4.15.0+-dbg.
Preparing to unpack linux-image-4.15.0+-dbg_4.15.0+-2_amd64.deb ...
Unpacking linux-image-4.15.0+-dbg (4.15.0+-2) ...
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed 
data is corrupt
dpkg-deb: error: subprocess  returned error exit status 2
dpkg: error processing archive linux-image-4.15.0+-dbg_4.15.0+-2_amd64.deb 
(--install):
 cannot copy extracted data for 
'./usr/lib/debug/lib/modules/4.15.0+/kernel/drivers/iio/pressure/zpa2326.ko' to 
'/usr/lib/debug/lib/modules/4.15.0+/kernel/drivers/iio/pressure/zpa2326.ko.dpkg-new':
 unexpected end of file or stream
Selecting previously unselected package linux-libc-dev.
Preparing to unpack linux-libc-dev_4.15.0+-2_amd64.deb ...
Unpacking linux-libc-dev (4.15.0+-2) ...
Setting up linux-headers-4.15.0+ (4.15.0+-2) ...
Setting up linux-image-4.15.0+ (4.15.0+-2) ...
update-initramfs: Generating /boot/initrd.img-4.15.0+
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_39.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver9_29.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module 
i915
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.15.0+
Found initrd image: /boot/initrd.img-4.15.0+
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-libc-dev (4.15.0+-2) ...
Errors were encountered while processing:
 linux-image-4.15.0+-dbg_4.15.0+-2_amd64.deb

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

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

[Mehdinefrance]

Thanks for your message Kai-Heng Feng.

I am puzzled when I click on the link you sent me, even after having
checked the help section
(https://wiki.ubuntu.com/Kernel/MainlineBuilds).

Is there any possibility for me to make a live-usb key with a mainline
kernel so that I can test it on my computer ? If so, is there any iso
image I could download ?

-- 
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 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.9~17.10.1

---
ubuntu-fan (0.12.9~17.10.1) artful; urgency=medium

  [ Andy Whitcroft ]
  * fanctl: fix config_filename when the interface does not have a width
(LP: #1737640)

 -- Stefan Bader   Tue, 30 Jan 2018 10:54:13
+0100

** Changed in: ubuntu-fan (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Invalid
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Won't Fix
Status in ubuntu-fan source package in Artful:
  Fix Released
Status in ubuntu-fan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

  [SRU Justification]

  == Impact ==

  Due to unexpectedly passing up a non-critical error to the ifup hooks,
  this causes network interfaces to not come up.

  == Fix ==

  This was fixed in Xenial (and already forward ported to Bionic)
  effectively allowing to bring up network interfaces via ifupdown after
  installing ubuntu-fan.

  == Testcase ==

  Basic installation with ifupdown method for configuring network
  interfaces (no longer default for Artful and later). Then installing
  ubuntu-fan and either reboot or use ifdown -a && ifup -a in case of
  being logged in locally. Without the fix interfaces will not come up
  properly.

  == Regression Risk ==

  Minimal, well tested in Xenial and not impacting Artful and later if
  ifupdown is not used.

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

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

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

[Dennis Pries]

#565 Nope.. Nothing. It's not a Laptop but a Mini-PC
(https://sp.ts.fujitsu.com/dmsp/Publications/public/ds-
esprimo-Q9000-estar5.pdf). It even does not seam to detect the USB
keyboard (no lights flashing or NUM-LOCK switching possible). Also I've
a black screen.

Simply dead. I tried a BIOS recovery in may ways (Data-Sheet says it
supports it, but nobody has described how to do it, so try-and-error was
the only option), but this also does not work. Reacts to nothing.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

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

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

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

  ---

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

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

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

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

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

  ---

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

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

  ---

  Affected Machines:

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

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

  ---

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

  ---

  Original Description:

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

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

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

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

  Thank you!!

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

[Kernel-packages] [Bug 1746903] Re: linux: 4.13.0-33.36 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.13.0-33.36 -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:
  In Progress
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 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: 1746904,1746905,1746907,1746909,1746910,1746912
  derivatives: 1746914
  -- 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/1746903/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

[David Emmett]

I have the same problem. The system fails to resume after hibernate. I
have tested it with the following kernels:

4.13.0.21 - works
4.13.0.25 - broken
4.13.0.31 - broken
4.13.0.31 - broken

-- 
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 1747902] Re: System does not resume after hibernate

[David Emmett]

Yes, this looks like exactly the same bug. It should perhaps be marked
as a duplicate of that one.

Thanks Sebastiaan.

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

Title:
  System does not resume after hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the update from linux-4.13.0-21-generic to
  linux-4.13.0-25-generic, resuming after hibernation no longer works.
  The problem persists after updates to 4.13.0-31-generic and
  4.13.0-32-generic.

  The system goes into hibernation correctly, shutting down properly
  when the power button is pressed (configured to hibernate system). But
  when the power button is pressed again (or the laptop lid opened), the
  system gets passed the grub menu and then hangs.

  On 4.13.0-21-generic, where hibernation works, the splash screen
  briefly displays a message about loading an img and then boots.

  From 4.13.0-25-generic, the system never reaches this stage. Nothing
  is ever logged in kernel.log or by dmesg, and the system hangs with a
  blank screen. The system is unresponsive to any input. I have to press
  and hold the power button, after which the system reboots as if from a
  fresh boot.

  Desired behavior is obviously that the system resumes after
  hibernation and restores itself to its previous state. Hibernation
  works perfectly on 4.13.0-21-generic, but not since then.

  I have attached the output from 4.13.0-21-generic and
  4.13.0-32-generic of the following for comparison

  $ uname -a > uname-a.log
  $ cat /proc/version_signature > version.log
  $ dmesg > dmesg.log
  $ sudo lspci -vvnn > lspci-vvnn.log

  My system is a Lenovo Thinkpad T460 with 16GB of RAM, and a 512GB SSD.
  I have 14.9GB of swap. The behavior is identical regardless of whether
  I have external screens, mice, keyboards, etc attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1982 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Feb  7 13:03:27 2018
  HibernationDevice: RESUME=UUID=3f54853d-1d7f-426b-9cfd-22ce1f6a1dc7
  InstallationDate: Installed on 2016-12-29 (404 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FNCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=70437d43-e174-4edf-97f8-613c1cb99b22 ro quiet splash 
UUID=3f54853d-1d7f-426b-9cfd-22ce1f6a1dc7 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-24 (106 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET58W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET58W(1.32):bd12/15/2017:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FNCTO1WW
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747902/+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 1747944] Re: mce errors since latest kernelupdate

[Achim Behrens]

Just saw that Dell revoked their A15 Bios Update for the Poweredge T20.
So i downgraded to Bios A14 and the /proc/cpuinfo now shows 0x22 as
microcode again. It was 0x23 on the revoked BIOS A15.

Looks like the mce errors are gone now on load.

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

Title:
  mce errors since latest kernelupdate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, running 16.04 server on a Dell Poweredge T20. Since latest
  meltdown/spectre Kernel update i get "mce: [Hardware Error]: Machine
  check events logged" shown in the logs. This happens when the server
  is compiling stuff scheduled per cron.

  the mce-log shows entries like: 
  Hardware event. This is not a software error.
  MCE 0
  CPU 0 BANK 0 
  TIME 1517991144 Wed Feb  7 09:12:24 2018
  MCG status:
  MCi status:
  Corrected error
  Error enabled
  MCA: Internal parity error
  STATUS 904f0005 MCGSTATUS 0
  MCGCAP c09 APICID 0 SOCKETID 0 
  CPUID Vendor Intel Family 6 Model 60

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-112-generic.
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Feb  7 16:49:09 2018
  HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99
  InstallationDate: Installed on 2017-05-17 (266 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge T20
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-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: 12/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0VD5HY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd12/26/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr:
  dmi.product.name: PowerEdge T20
  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/1747944/+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 1727651] Re: Ubuntu freezes after suspend [ Lenovo T460s / Ubuntu 17.10 ]

[Yerong Li]

I had a similar issue  have a with lscpu outputs:
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  2
 -line CPU(s) list: 0,1
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   AuthenticAMD
CPU family:  21
Model:   112
Model name:  AMD A9-9420 RADEON R5, 5 COMPUTE CORES 2C+3G


My laptop can suspend and re-login on ubuntu 17.10, but on every re-login I 
found the system will freeze after a while.

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

Title:
  Ubuntu freezes after suspend [ Lenovo T460s / Ubuntu 17.10 ]

Status in linux package in Ubuntu:
  Expired

Bug description:
  Closing the lid will suspend Ubuntu (17.10). After opening the lid the
  screen is either black (no backlight) or the lock screen is shown but
  the system is freezed. There is no further reaction from the system (I
  can't switch via Ctrl+Alt+F1..9. Just MagicKey+RB would reboot the
  system.

  I have appended my syslog from the suspend to the freeze. What other
  information could I provide?

  
  uname -a
  4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  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/controlC0:  thomass1239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:40:26 2017
  HibernationDevice: RESUME=UUID=811ba335-5e49-4e96-959c-d98c3d644c5a
  InstallationDate: Installed on 2017-10-20 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20FAS05P00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root 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: 09/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET60W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS05P00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET60W(1.28):bd09/26/2017:svnLENOVO:pn20FAS05P00:pvrThinkPadT460s:rvnLENOVO:rn20FAS05P00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS05P00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727651/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

[Sebastiaan Breedveld]

In addition to my post #78: same kernel, so same problem persists in
18.04 alpha (Bionic Beaver). Installing 4.14.13-041413 (and hibernate
after a new reboot) as suggested above solved this problem for me.

I would strongly suggest that the Bionic developer team will consider to
include this version in the release.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1708409] Re: kdump service does not start after configure/reboot

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-1

---
makedumpfile (1:1.6.3-1) unstable; urgency=medium

  * New upstream release. Main new feature:
o Support new kernels
 - The supported kernel is updated to 4.14.8 in this version. (LP: #1746299)
   4.14.9 and later can't be filtered correctly due to inappropriate 
VMCOREINFO,
   it will be resolved in kernel 4.15.

  * Changelog:
o New feature
- [PATCH v2] x86_64: Take care of init_level4_pgt rename in kernel (by 
Pratyush Anand) 64bd5db
- [PATCH v2] Fix SECTION_MAP_MASK for kernel >= v.13 (by Pratyush 
Anand) 4bf4f2b
- [PATCH v2] book3s/ppc64: Lower the max real address to 53 bits for 
kernels >= v4.11
  (by Bhupesh Sharma) 6c83e74
- [PATCH v3 1/4] Support symbol __cpu_online_mask (by Takao Indoh) 
3b11c00
- [PATCH] ppc64: update hash page table geometry (by Hari Bathini) 
3c39f13
- [PATCH] handle renamed init_level4_pgt -> init_top_pgt (by Jeff 
Mahoney) 5e54d53

o Bugfix
- [PATCH v2] arm64: Fix page table walk of 1GB section (by Bradley 
Bolen) 27508f1
- [PATCH v2 1/2] ppc64: set page_offset in get_versiondep_info_ppc64() 
(by Pingfan Liu) 52319d2
- [PATCH v2 2/2] ppc64: get the info of mem reserved for crashkernel 
(by Pingfan Liu) c7fcbbc
- [PATCH v3 3/4] sadump: Fix a KASLR problem of sadump (by Takao Indoh) 
b4f7d95
- [PATCH v3 4/4] sadump: Fix a KASLR problem of sadump while kdump is 
working (by Takao Indoh) 13d3059
- [PATCH 2/2] Fix 'kernel_version' variable being uninitialized & 
introduce minor reorganization
  (by Bhupesh Sharma) d1ffe82
- [PATCH 1/2] Fix off-by-one errors in exclude_segment() (by Petr 
Tesarik) 590f35e
- [PATCH 2/2] Fix physical-to-virtual conversion in exclude_segment() 
(by Petr Tesarik) 6c1bf2a

o Cleanup
- [PATCH] Fix formatting problems in header file (by Eric DeVolder) 
cefea9e
- [PATCH v3 2/4] Introduce vtop4_x86_64_pagetable (by Takao Indoh) 
6de5d37
- [PATCH 1/2] Fix compilation warnings on ppc64/ppc64le platforms (by 
Bhupesh Sharma) 0df157a
- [PATCH] Make good use of is_cyclic_region() (by Atsushi Kumagai) 
6bfd7a3
- [PATCH] Fix the regression about getting kernel version (by Atsushi 
Kumagai) 254c116
- [PATCH] Update maintainers (by Atsushi Kumagai) 9d3147e

  * Use multi-user.target. (LP: #1708409)
  * kdump-tools Recommends initramfs-tools-core.
  * Add myself as uploader.
  * Move Vcs control fields to salsa.

 -- Thadeu Lima de Souza Cascardo   Tue, 06 Feb
2018 12:53:14 -0200

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  kdump service does not start after configure/reboot

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

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-1

---
makedumpfile (1:1.6.3-1) unstable; urgency=medium

  * New upstream release. Main new feature:
o Support new kernels
 - The supported kernel is updated to 4.14.8 in this version. (LP: #1746299)
   4.14.9 and later can't be filtered correctly due to inappropriate 
VMCOREINFO,
   it will be resolved in kernel 4.15.

  * Changelog:
o New feature
- [PATCH v2] x86_64: Take care of init_level4_pgt rename in kernel (by 
Pratyush Anand) 64bd5db
- [PATCH v2] Fix SECTION_MAP_MASK for kernel >= v.13 (by Pratyush 
Anand) 4bf4f2b
- [PATCH v2] book3s/ppc64: Lower the max real address to 53 bits for 
kernels >= v4.11
  (by Bhupesh Sharma) 6c83e74
- [PATCH v3 1/4] Support symbol __cpu_online_mask (by Takao Indoh) 
3b11c00
- [PATCH] ppc64: update hash page table geometry (by Hari Bathini) 
3c39f13
- [PATCH] handle renamed init_level4_pgt -> init_top_pgt (by Jeff 
Mahoney) 5e54d53

o Bugfix
- [PATCH v2] arm64: Fix page table walk of 1GB section (by Bradley 
Bolen) 27508f1
- [PATCH v2 1/2] ppc64: set page_offset in get_versiondep_info_ppc64() 
(by Pingfan Liu) 52319d2
- [PATCH v2 2/2] ppc64: get the info of mem reserved for crashkernel 
(by Pingfan Liu) c7fcbbc
- [PATCH v3 3/4] sadump: Fix a KASLR problem of sadump (by Takao Indoh) 
b4f7d95
- [PATCH v3 4/4] sadump: Fix a KASLR problem of sadump while kdump is 
working (by Takao Indoh) 13d3059
- [PATCH 2/2] Fix 'kernel_version' variable being uninitialized & 
introduce minor reorganization
  (by Bhupesh Sharma) d1ffe82
- [PATCH 1/2] Fix off-by-one errors in exclude_segment() (by Petr 
Tesarik) 590f35e
- [PATCH 2/2] Fix physical-to-virtual conversion in exclude_segment() 
(by Petr Tesarik) 6c1bf2a

o Cleanup
- [PATCH] Fix formatting problems in header file (by Eric DeVolder) 
cefea9e
- [PATCH v3 2/4] Introduce vtop4_x86_64_pagetable (by Takao Indoh) 
6de5d37
- [PATCH 1/2] Fix compilation warnings on ppc64/ppc64le platforms (by 
Bhupesh Sharma) 0df157a
- [PATCH] Make good use of is_cyclic_region() (by Atsushi Kumagai) 
6bfd7a3
- [PATCH] Fix the regression about getting kernel version (by Atsushi 
Kumagai) 254c116
- [PATCH] Update maintainers (by Atsushi Kumagai) 9d3147e

  * Use multi-user.target. (LP: #1708409)
  * kdump-tools Recommends initramfs-tools-core.
  * Add myself as uploader.
  * Move Vcs control fields to salsa.

 -- Thadeu Lima de Souza Cascardo   Tue, 06 Feb
2018 12:53:14 -0200

** Changed in: makedumpfile (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool 

[Kernel-packages] [Bug 1746937] Re: linux-aws: 4.4.0-1013.13 -proposed tracker

[Kamal Mostafa]

** Summary changed:

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

** 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) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

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 1745646] Re: Battery drains when laptop is off (shutdown)

[Gopal]

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

** No longer affects: acpi (Ubuntu)

** Also affects: acpi (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/1745646

Title:
  Battery drains when laptop is off  (shutdown)

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

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

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

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

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

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

[Joseph Salisbury]

The first bisect report the following commit as the first bad commit:
2f34c1231bfc ("Merge tag 'drm-for-v4.12' of 
git://people.freedesktop.org/~airlied/linux")

However, because this commit is a merge, I have to perform another round
of bisecting between this commits parents.  I'll have another update
shortly.

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

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

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

[Kamal Mostafa]

Thanks for the confirmation Paul, and thanks to all for the assistance
with testing and isolation.

We will be deploying this fix (the 'retpoline' patch set) in the next
version of the linux-aws kernel (4.4.0-1051.60) and the Xenial generic
kernel (4.4.0-113.136).

We'll post here once those builds land in the -proposed archive.

-- 
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 1747909] Re: 4.13 kernel panic on kfree (security_sk_free)

[Rafael David Tinoco]

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

** This bug has been marked a duplicate of bug 1734327
   Kernel panic on a nfsroot system

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

Title:
  4.13 kernel panic on kfree (security_sk_free)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm frequently facing this issue with Artful kernels 4.13:

  [ 1317.490018] general protection fault:  [#1] SMP NOPTI
  [ 1317.491099] Modules linked in: ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter nfsv3 nfs_acl nfs lockd grace fscache edac_mce_amd 
qemu_fw_cfg pata_acpi sunrpc ip_tables x_tables bridge stp llc virtio_scsi 
input_leds kvm_amd kvm irqbypass virtio_blk virtio_net mac_hid
  [ 1317.494814] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.13.0-32-generic 
#35-Ubuntu
  [ 1317.496199] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1317.497373] task: 98a1ad675d00 task.stack: a76dc18f8000
  [ 1317.498274] RIP: 0010:kfree+0x53/0x160
  [ 1317.498852] RSP: 0018:98a1bfd03768 EFLAGS: 00010207
  [ 1317.499620] RAX:  RBX: 2e6c61636974706f RCX: 
0006
  [ 1317.500665] RDX: 2ecc30d0 RSI: 00010080 RDI: 
6762
  [ 1317.501677] RBP: 98a1bfd03780 R08: 00025d80 R09: 
a3bbd839
  [ 1317.502704] R10: 00b97c9557a5d1c0 R11:  R12: 
98a1a8430800
  [ 1317.503736] R13: a37a3dbe R14: 98a1a8430800 R15: 
98a1a8430800
  [ 1317.504753] FS:  () GS:98a1bfd0() 
knlGS:
  [ 1317.505888] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1317.506736] CR2: 7fbf9c9254d0 CR3: 000413c0a000 CR4: 
000406e0
  [ 1317.507753] Call Trace:
  [ 1317.508168]  
  [ 1317.508534]  security_sk_free+0x3e/0x50
  [ 1317.509135]  __sk_destruct+0x108/0x190
  [ 1317.509711]  sk_destruct+0x20/0x30
  [ 1317.510254]  __sk_free+0x82/0xa0
  [ 1317.510771]  sk_free+0x19/0x20
  [ 1317.511267]  sock_put+0x14/0x20
  [ 1317.511763]  tcp_v4_rcv+0x94d/0x9d0
  [ 1317.512319]  ? virtio_pci_probe+0xd0/0x130
  [ 1317.513010]  ip_local_deliver_finish+0x5c/0x1f0
  [ 1317.513800]  ip_local_deliver+0x6f/0xe0
  [ 1317.514495]  ? ip_rcv_finish+0x410/0x410
  [ 1317.515440]  ip_rcv_finish+0x120/0x410
  [ 1317.516193]  ip_rcv+0x28c/0x3a0
  [ 1317.516944]  ? packet_rcv+0x44/0x440
  [ 1317.517635]  __netif_receive_skb_core+0x39a/0xaa0
  [ 1317.518503]  ? dev_queue_xmit+0x10/0x20
  [ 1317.519279]  ? br_dev_queue_push_xmit+0x7a/0x140 [bridge]
  [ 1317.520262]  __netif_receive_skb+0x18/0x60
  [ 1317.520941]  ? __netif_receive_skb+0x18/0x60
  [ 1317.521638]  netif_receive_skb_internal+0x3f/0x3f0
  [ 1317.522408]  netif_receive_skb+0x1c/0x70
  [ 1317.523021]  br_netif_receive_skb+0x34/0x50 [bridge]
  [ 1317.523771]  br_pass_frame_up+0xcd/0x150 [bridge]
  [ 1317.524478]  ? br_port_flags_change+0x20/0x20 [bridge]
  [ 1317.525236]  br_handle_frame_finish+0x125/0x540 [bridge]
  [ 1317.526020]  ? cpumask_next_and+0x2c/0x40
  [ 1317.526638]  ? br_handle_local_finish+0x40/0x40 [bridge]
  [ 1317.527423]  br_handle_frame+0x156/0x300 [bridge]
  [ 1317.528156]  ? csum_partial+0x11/0x20
  [ 1317.528725]  __netif_receive_skb_core+0x212/0xaa0
  [ 1317.529432]  ? skb_checksum+0x35/0x50
  [ 1317.530012]  ? skb_append_datato_frags+0x200/0x200
  [ 1317.530729]  ? reqsk_fastopen_remove+0x140/0x140
  [ 1317.531415]  __netif_receive_skb+0x18/0x60
  [ 1317.532037]  ? __netif_receive_skb+0x18/0x60
  [ 1317.532684]  netif_receive_skb_internal+0x3f/0x3f0
  [ 1317.533394]  ? dev_gro_receive+0x2dc/0x480
  [ 1317.534029]  napi_gro_receive+0xc2/0xe0
  [ 1317.534628]  receive_buf+0x218/0xf70 [virtio_net]
  [ 1317.535332]  ? vring_unmap_one+0x1b/0x80
  [ 1317.535931]  virtnet_poll+0x173/0x268 [virtio_net]
  [ 1317.536645]  net_rx_action+0x13b/0x380
  [ 1317.537224]  ? skb_recv_done+0x30/0x40 [virtio_net]
  [ 1317.537962]  __do_softirq+0xde/0x2a5
  [ 1317.538553]  irq_exit+0xb6/0xc0
  [ 1317.539056]  do_IRQ+0x80/0xd0
  [ 1317.539530]  common_interrupt+0x1af/0x1af
  [ 1317.540139]  
  [ 1317.540500] RIP: 0010:native_safe_halt+0x6/0x10
  [ 1317.541178] RSP: 0018:a76dc18fbe70 EFLAGS: 0246 ORIG_RAX: 
ff8d
  [ 1317.542262] RAX:  RBX: 98a1ad675d00 RCX: 

  [ 1317.543302] RDX:  RSI:  RDI: 

  [ 1317.544338] RBP: a76dc18fbe70 R08: 0002 R09: 
98a1ad6d3400
  [ 1317.545410] R10:  R11: 0400 R12: 
0002
  [ 1317.546654] R13: 98a1ad675d00 R14:  R15: 

  [ 1317.547722]  default_idle+0x20/0x100
  [ 1317.548285]  arch_cpu_idle+0xf/0x20
  [ 1317.548825]  default_idle_call+0x23/0x30
  [ 1317.549428]  do_idle+0x17d/0x200
  [ 

[Kernel-packages] [Bug 1685899] Comment bridged from LTC Bugzilla

[bugproxy]

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

--- Comment From cha...@us.ibm.com 2018-02-07 13:40 EDT---
I am sorry but I won't be able to investigate this issue any longer and since 
there aren't JFS maintainers within the LTC, it is unlikely I can turn this 
over to anyone else. Since the middle of 2017, there have been a few more 
commits to JFS but they didn't appear to be helpful in this area affected.

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

Title:
  [Ubuntu 17.04] - JFS related call traces and system enters xmon when
  rebooted after installation

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

Bug description:
  Issue:
  
  JFS related call traces and system enters xmon when rebooted after 
installation 

  Steps to reproduce:
  -
  1 - Install Ubuntu 17.04 the system with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  2 -After installation when rebooted it gives out call traces like as
  below:

  [3.895246] Unable to handle kernel paging request for data at address 
0x
  [3.895278] Faulting instruction address: 0xd4c5df1c
  [3.895284] Oops: Kernel access of bad area, sig: 11 [#1]
  [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA 
  [3.895290] pSeries
  [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi 
crc32c_vpmsum
  [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic 
#16-Ubuntu
  [3.895304] task: c00381d3c800 task.stack: c00381fd
  [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: 
c01279d0
  [3.895310] REGS: c00381fd3500 TRAP: 0300   Not tainted  
(4.9.0-15-generic)
  [3.895313] MSR: 8280b033 [
3.895322]   CR: 48008804  XER: 0001
  [3.895324] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 
  GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 
  GPR08:  00180e97  d4c6a608 
  GPR12: c01279d0 cfb90e00   
  GPR16:     
  GPR20:     
  GPR24:  1000  d4c72b38 
  GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 
  NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs]
  [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs]
  [3.895374] Call Trace:
  [3.895378] [c00381fd3780] [d4c5de6c] 
__get_metapage+0x154/0x6f0 [jfs] (unreliable)
  [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs]
  [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs]
  [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 
[jfs]
  [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240
  [3.895402] [c00381fd3b00] [c032e8a8] 
walk_component+0x2d8/0x3f0
  [3.895406] [c00381fd3b70] [c032eb94] 
link_path_walk+0x1d4/0x600
  [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480
  [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160
  [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380
  [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0
  [3.895424] Instruction dump:
  [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 
41820460 
  [3.895433] ebdd0030 41920034 e91d0008 e93f0038  811e 
80e70090 39080001 
  [3.895441] ---[ end trace c2aa9ba09ea05eac ]---
  [3.895443] 
  [4.088560] systemd-journald[925]: Received request to flush runtime 
journal from PID 1
  [4.362062] crypto_register_alg 'aes' = 0
  [4.362112] crypto_register_alg 'cbc(aes)' = 0
  [4.362150] crypto_register_alg 'ctr(aes)' = 0
  [4.362191] crypto_register_alg 'xts(aes)' = 0
  [4.366949] pseries_rng: Registering IBM pSeries RNG driver

  When I first connected to the LPAR, it was unresponsive so I restarted
  it from the HMC and surprisingly it came up to the login prompt and I
  logged into the shell. I proceeded to install the matching linux-
  image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the
  installation of the matching dbgsym wasn't as helpful as I wanted it
  to be. objdump, crash tool, or addr2line wouldn't give me the source
  line correspond to the NIP address.

  I then restarted the LPAR with xmon enabled and it would drop to 

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[Kamal Mostafa]

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-aws (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => Kamal Mostafa (kamalmostafa)

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

** Also affects: sssd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** No longer affects: sssd (Ubuntu)

** No longer affects: sssd (Ubuntu Xenial)

** Changed in: linux-aws (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1746946] Re: linux-aws: 4.4.0-1051.60 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

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

Title:
  linux-aws: 4.4.0-1051.60 -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 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:
  Invalid
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: 1746936

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

[Kamal Mostafa]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1051.60 -proposed tracker

** 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) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

Title:
  linux-aws: 4.4.0-1051.60 -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 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:
  Invalid
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: 1746936

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746946/+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

[Peridot]

** Summary changed:

- kernel crashes unless IOMMU is disabled on Ryzen 1800X 
+ kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

** Description changed:

  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.
  
- Lots of AMD-Vi logged events and I get irq crashes or acpi hangups with
- a normal boot. How I it to work is to disable IOMMU in the BIOS and add
- "iommu=soft" to the kernel booting options in grub.
+ 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.
  
  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
+  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.
+  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
+  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

** Description changed:

  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.
+ 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: 

[Kernel-packages] [Bug 1747902] Re: System does not resume after hibernate

[Sebastiaan Breedveld]

I would say this is the same bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094

Can you hit "affects me too" there?

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

Title:
  System does not resume after hibernate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the update from linux-4.13.0-21-generic to
  linux-4.13.0-25-generic, resuming after hibernation no longer works.
  The problem persists after updates to 4.13.0-31-generic and
  4.13.0-32-generic.

  The system goes into hibernation correctly, shutting down properly
  when the power button is pressed (configured to hibernate system). But
  when the power button is pressed again (or the laptop lid opened), the
  system gets passed the grub menu and then hangs.

  On 4.13.0-21-generic, where hibernation works, the splash screen
  briefly displays a message about loading an img and then boots.

  From 4.13.0-25-generic, the system never reaches this stage. Nothing
  is ever logged in kernel.log or by dmesg, and the system hangs with a
  blank screen. The system is unresponsive to any input. I have to press
  and hold the power button, after which the system reboots as if from a
  fresh boot.

  Desired behavior is obviously that the system resumes after
  hibernation and restores itself to its previous state. Hibernation
  works perfectly on 4.13.0-21-generic, but not since then.

  I have attached the output from 4.13.0-21-generic and
  4.13.0-32-generic of the following for comparison

  $ uname -a > uname-a.log
  $ cat /proc/version_signature > version.log
  $ dmesg > dmesg.log
  $ sudo lspci -vvnn > lspci-vvnn.log

  My system is a Lenovo Thinkpad T460 with 16GB of RAM, and a 512GB SSD.
  I have 14.9GB of swap. The behavior is identical regardless of whether
  I have external screens, mice, keyboards, etc attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1982 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Feb  7 13:03:27 2018
  HibernationDevice: RESUME=UUID=3f54853d-1d7f-426b-9cfd-22ce1f6a1dc7
  InstallationDate: Installed on 2016-12-29 (404 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20FNCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=70437d43-e174-4edf-97f8-613c1cb99b22 ro quiet splash 
UUID=3f54853d-1d7f-426b-9cfd-22ce1f6a1dc7 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-24 (106 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET58W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET58W(1.32):bd12/15/2017:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FNCTO1WW
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   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
  
  backports: 1746904,1746905,1746907,1746909,1746910,1746912
  derivatives: 1746914
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 07. February 2018 10:01 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 07. February 2018 17:31 UTC

** 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: 1746904,1746905,1746907,1746909,1746910,1746912
  derivatives: 1746914
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Wednesday, 07. February 2018 17:31 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/1746903

Title:
  linux: 4.13.0-33.36 -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:
  Confirmed
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 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: 1746904,1746905,1746907,1746909,1746910,1746912
  derivatives: 1746914
  -- 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/1746903/+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 1747746] Re: [Artful/Bionic] [Config] enable EDAC_GHES for ARM64

[Manoj Iyer]

- Power8-
Where edac_ghes config is not enabled 

-- before patch --
ubuntu@entei:~$ dmesg | grep -i -E "EDAC|GHES"
[0.770577] EDAC MC: Ver: 3.0.0
ubuntu@entei:~$

-- after patch -- 
ubuntu@entei:~$ uname  -a
Linux entei 4.14.0-17-generic #20~configs+test.2-Ubuntu SMP Tue Feb 6 20:41:16 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@entei:~$ dmesg | grep -i -E "EDAC|GHES"
[1.073492] EDAC MC: Ver: 3.0.0
ubuntu@entei:~$

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

Title:
  [Artful/Bionic] [Config] enable EDAC_GHES for ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Enable CONFIG_EDAC_GHES option for ARM64, so that the memory errors are 
processed and reported to the user space.

  [Test]
  Test kernel is available in the PPA: 
https://launchpad.net/~centriq-team/+archive/ubuntu/lp1747746
  Tested on QDF2400 platform with Artful user-space and Bionic 4.14 kernel. 
Please see comment #2 for results.

  [Regression Potential]
  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747746/+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 1568341] Re: Boot hangs at: /scripts/local-premount/uswsusp

[Christopher M. Penalver]

Closing this report, as not reproducible on my hardware. All others
please file a new report.

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

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

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

Title:
  Boot hangs at: /scripts/local-premount/uswsusp

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When booting Ubuntu kernels  4.4.0-16 through  4.4.0-18 (either by default or 
upstart), it hangs during boot noting as per the attached screenshot:
  Begin: Running /scripts/local-premount ...

  With debug=y kernel parameter it hangs at:
  /scripts/local-premount/uswsusp

  This doesn't happen via 4.4.0-15.

  Git bisect revealed:
  # first bad commit: [746a312bf960810a7ccfb16eefeec68a335392b4] UBUNTU: Start 
new release

  WORKAROUND: Uninstall package:
  uswsusp

  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  moniker1927 F pulseaudio
   /dev/snd/controlC1:  moniker1927 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c099059e-62ee-4a3a-8dc7-64bf4eb0c960
  InstallationDate: Installed on 2015-12-18 (112 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite S55-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/14/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.10
  dmi.board.name: 06F1
  dmi.board.vendor: FF50
  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.:bvr5.10:bd10/14/2015:svnTOSHIBA:pnSatelliteS55-C:pvrPSPTJU-006005:rvnFF50:rn06F1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-C
  dmi.product.version: PSPTJU-006005
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568341/+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 1568341] Re: Boot hangs at: /scripts/local-premount/uswsusp

[Sebastiaan Breedveld]

@Christopher: perhaps. My system became somewhat convoluted while trying
to get hibernation to work somehow.

Clean test:
- disabled Secure Boot, just to be sure
- installed Xubuntu 18.04 alpha 2, most recent daily image 
- updated and installed only uswsusp
- reboot

Boot hangs at the exact same point as with the OP. However, after a 5-10
minutes wait, the system informs me that it cannot find the resume
device, and I could press [Enter] to boot normally.

It seems that uswsusp is installed without proper (forced) configuration:
1) The UUID displayed it not part of my system
2) I found this reference in /etc/uswsusp.conf
3) I disabled cryptoswap, and set resume_device to my swap partition (just to 
make things easy)
4) I used s2disk, and see a progress bar that the session is written to disk
5) After booting, still the long wait, and uswsusp is still looking at the 
wrong device (why?)
6) I manually enter my swap partition on request, and see that the system is 
being loaded from disk
7) Screen stays black

So I am not sure what problem I am running into. I think uswsusp is not
configured, and some configuration should be forced before enabling it
after installation. Also, the wait could be reduced.

The black screen problem may be related to kernel 4.13 (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094 ), a
behavior I also encountered with 16.04.3 LTS and pm-hibernate on the
same system (downgrading to 4.10 helped).

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

Title:
  Boot hangs at: /scripts/local-premount/uswsusp

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When booting Ubuntu kernels  4.4.0-16 through  4.4.0-18 (either by default or 
upstart), it hangs during boot noting as per the attached screenshot:
  Begin: Running /scripts/local-premount ...

  With debug=y kernel parameter it hangs at:
  /scripts/local-premount/uswsusp

  This doesn't happen via 4.4.0-15.

  Git bisect revealed:
  # first bad commit: [746a312bf960810a7ccfb16eefeec68a335392b4] UBUNTU: Start 
new release

  WORKAROUND: Uninstall package:
  uswsusp

  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  moniker1927 F pulseaudio
   /dev/snd/controlC1:  moniker1927 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=c099059e-62ee-4a3a-8dc7-64bf4eb0c960
  InstallationDate: Installed on 2015-12-18 (112 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA Satellite S55-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-01-20 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/14/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 5.10
  dmi.board.name: 06F1
  dmi.board.vendor: FF50
  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.:bvr5.10:bd10/14/2015:svnTOSHIBA:pnSatelliteS55-C:pvrPSPTJU-006005:rvnFF50:rn06F1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55-C
  dmi.product.version: PSPTJU-006005
  dmi.sys.vendor: TOSHIBA

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

[bugproxy]

--- Comment From frede...@fr.ibm.com 2018-02-07 11:21 EDT---
Hi Joseph,
I tested the kernel your provided and that works perfectly.
Thanks,

F.

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

Title:
  Ubuntu 17.10 crashes on vmalloc.c

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  == Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
  When running Ubuntu 17.10 on POWER9, I got the following error:

  [409038.118908] WARNING: CPU: 47 PID: 294 at 
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
  [409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler 
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv 
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum 
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
ttm drm tg3 ahci libahci
  [409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW   
4.13.0-12-generic #13-Ubuntu
  [409038.118934] Workqueue: events pcpu_balance_workfn
  [409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
  [409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR: 

  [409038.118937] REGS: c03fe3be3810 TRAP: 0700   Tainted: GW   
 (4.13.0-12-generic)
  [409038.118938] MSR: 9282b033 
  [409038.118944]   CR: 24024828  XER: 2004
  [409038.118944] CFAR: c032bdb8 SOFTE: 1
  GPR00: 2df0 c03fe3be3a90 c15e3000 
c000203fff6b6880
  GPR04: c000203fff223608 0008 c000203fff6b6888 

  GPR08: 2df0 0800 0160 
c000203fff6b6888
  GPR12: 0002 cfaded80 c0f6c050 
c03fe3be3bc0
  GPR16: 0010  c189daf8 
c000203fff223608
  GPR20: 2f50 c000203fff2235f8 c000203fff223600 

  GPR24:  c000203fff6b6888 0001 
2f50
  GPR28: 0002 000f d800 
d000
  [409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
  [409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
  [409038.118965] Call Trace:
  [409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0 
(unreliable)
  [409038.118968] [c03fe3be3b60] [c02f5fd4] 
pcpu_create_chunk+0xb4/0x1b0
  [409038.118970] [c03fe3be3ba0] [c02f7890] 
pcpu_balance_workfn+0x600/0x960
  [409038.118972] [c03fe3be3ca0] [c01205d8] 
process_one_work+0x298/0x5a0
  [409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
  [409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
  [409038.118979] [c03fe3be3e30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
  [409038.118980] Instruction dump:
  [409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 
3b40 e953

   
  ---uname output---
  4.13.0-12-generic

  == Comment: #3 - ANEESH K. K V  - 2017-12-20 05:59:13 ==
  https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au

  The above may be related?

  Related discussions
  https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz

  -aneesh

  == Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
  I just tested with kernel 4.15.0-041500rc4 and I didn't see a problem so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1739498/+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 1747069] Re: artful 4.13 i386 kernels crash after memory hotplug remove

[Colin Ian King]

Requires backports of commits:

a86d69d58aad561b6bbb44e60f74c41cd4b5f3ab
ed067d4a859ff696373324c5061392e013a7561a
f7f99100d8d95dbcf09e0216a143211e79418b9f
a4a3ede2132ae0863e2d43e06f9b5697c51a7a3b
ea1f5f3712afe895dfa4176ec87376b4a9ac23be

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

Title:
  artful 4.13 i386 kernels crash after memory hotplug remove

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It seems all of the artful 4.13 are crashing on i386 install when
  memory hotplug removal is attempted.  This crash occurs a few seconds
  after the removal.  I have done a gross bisect back to the first
  4.13.0-11 which is also affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747069/+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 1685849] Re: package linux-signed-image-4.10.0-19-generic 4.10.0-19.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package linux-signed-image-4.10.0-19-generic 4.10.0-19.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed package in Ubuntu:
  Invalid

Bug description:
  Failed during upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-signed-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 24 17:48:30 2017
  DuplicateSignature:
   package:linux-signed-image-4.10.0-19-generic:4.10.0-19.21
   Setting up linux-signed-image-4.10.0-19-generic (4.10.0-19.21) ...
   cp: cannot stat '/boot/vmlinuz-4.10.0-19-generic': No such file or directory
   dpkg: error processing package linux-signed-image-4.10.0-19-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-15 (221 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.10.0-19-generic 4.10.0-19.21 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (9 days ago)

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

[Khaled El Mously]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-113.136 -proposed tracker

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

-- 
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:
  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: 1746937,1746938
  derivatives: 1746939,1746941,1746942,1746944,1746945,1746946

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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

[Oliver R.]

I must correct my post #77: The X200 now shows the bug, but differently.
There is no blank screen, but the last screen before hibernation is
visible. Other than that, the system is absolutely frozen as in the
other cases. So this is an example of a pre-i3 processor with the bug
being present.

-- 
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 1700980] Re: Invalid EA on pre 4.9 kernels

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16043

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

Title:
  Invalid EA on pre 4.9 kernels

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-06-28 08:00:40 ==
  When a process accesses an invalid EA it results in a SEGV signal being
  sent to the process, which typically results in the process being
  killed. Process death isn't instantaneous however, the process may catch
  the SEGV signal and continue somehow, or the kernel may start writing a
  core dump for the process, either of which means it's possible for the
  process to be preempted while its processing the SEGV but before it's
  been killed.

  We need to have this fix on kernel 4.4 and 4.8:

  https://patchwork.ozlabs.org/patch/779346/

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  mce errors since latest kernelupdate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, running 16.04 server on a Dell Poweredge T20. Since latest
  meltdown/spectre Kernel update i get "mce: [Hardware Error]: Machine
  check events logged" shown in the logs. This happens when the server
  is compiling stuff scheduled per cron.

  the mce-log shows entries like: 
  Hardware event. This is not a software error.
  MCE 0
  CPU 0 BANK 0 
  TIME 1517991144 Wed Feb  7 09:12:24 2018
  MCG status:
  MCi status:
  Corrected error
  Error enabled
  MCA: Internal parity error
  STATUS 904f0005 MCGSTATUS 0
  MCGCAP c09 APICID 0 SOCKETID 0 
  CPUID Vendor Intel Family 6 Model 60

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-112-generic.
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Feb  7 16:49:09 2018
  HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99
  InstallationDate: Installed on 2017-05-17 (266 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge T20
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-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: 12/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0VD5HY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd12/26/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr:
  dmi.product.name: PowerEdge T20
  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/1747944/+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 1747944] [NEW] mce errors since latest kernelupdate

[Achim Behrens]

Public bug reported:

Hi, running 16.04 server on a Dell Poweredge T20. Since latest
meltdown/spectre Kernel update i get "mce: [Hardware Error]: Machine
check events logged" shown in the logs. This happens when the server is
compiling stuff scheduled per cron.

the mce-log shows entries like: 
Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 0 
TIME 1517991144 Wed Feb  7 09:12:24 2018
MCG status:
MCi status:
Corrected error
Error enabled
MCA: Internal parity error
STATUS 904f0005 MCGSTATUS 0
MCGCAP c09 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 6 Model 60

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-112-generic 4.4.0-112.135
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-112-generic.
AplayDevices: aplay: device_list:268: no soundcards found...
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: arecord: device_list:268: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Wed Feb  7 16:49:09 2018
HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99
InstallationDate: Installed on 2017-05-17 (266 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge T20
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-112-generic N/A
 linux-backports-modules-4.4.0-112-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: 12/26/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0VD5HY
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd12/26/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr:
dmi.product.name: PowerEdge T20
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  mce errors since latest kernelupdate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, running 16.04 server on a Dell Poweredge T20. Since latest
  meltdown/spectre Kernel update i get "mce: [Hardware Error]: Machine
  check events logged" shown in the logs. This happens when the server
  is compiling stuff scheduled per cron.

  the mce-log shows entries like: 
  Hardware event. This is not a software error.
  MCE 0
  CPU 0 BANK 0 
  TIME 1517991144 Wed Feb  7 09:12:24 2018
  MCG status:
  MCi status:
  Corrected error
  Error enabled
  MCA: Internal parity error
  STATUS 904f0005 MCGSTATUS 0
  MCGCAP c09 APICID 0 SOCKETID 0 
  CPUID Vendor Intel Family 6 Model 60

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-112-generic.
  AplayDevices: aplay: device_list:268: no soundcards found...
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: arecord: device_list:268: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Feb  7 16:49:09 2018
  HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99
  InstallationDate: Installed on 2017-05-17 (266 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge T20
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 

[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WestonXT

[Alvin Huan]

Can we fix this issue in Ubuntu 16.04 "linux-hwe" kernel as well? in
case, end user try to install Ubuntu 16.04.4 on their Raven+WestonXT
platform, they will run into this issue.

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

Title:
  boot failure on AMD Raven + WestonXT

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Triaged
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:

  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
  next-4.16=052c299080cd6859f82a8154a7a673fafabe644c

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1742759/+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 1742759] Re: boot failure on AMD Raven + WestonXT

[Alvin Huan]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1742759

Title:
  boot failure on AMD Raven + WestonXT

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Triaged
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:

  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
  next-4.16=052c299080cd6859f82a8154a7a673fafabe644c

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1742759/+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 1686727] Re: Kernel 4.10.0-20-generic #22-Ubuntu SMP crashes VERY often on Dell Latitude E5530

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Kernel 4.10.0-20-generic #22-Ubuntu SMP crashes VERY often on Dell
  Latitude E5530

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I already reported problems with kernel 4.10.0-19, but now I have even
  more problems with 4.10.0-20-generic!!! This new kernel seems to crash
  even more often than the previous one: twice in the last 30 minutes!!!

  You'll find attached the syslog of the recent events...

  I'll apport-collect as soon as I have an id to report to.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guillaume  17435 F pulseaudio
guillaume  19236 F pulseaudio
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=34aa2e74-6bb4-4c71-8ceb-a180d7199e68
  InstallationDate: Installed on 2012-12-06 (1602 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. Latitude E5530 non-vPro
  Package: linux 3.11.0.23.24 [origin: unknown]
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=62582629-4937-4cc6-b2e1-f9a624d18561 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164.1
  Tags: zesty third-party-packages
  Uname: Linux 4.10.0-20-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: Upgraded to zesty on 2016-11-17 (160 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0XJY67
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn0XJY67:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5530 non-vPro
  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/1686727/+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 1746903] Re: linux: 4.13.0-33.36 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.13.0-33.36 -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:
  Fix Committed
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: 1746904,1746905,1746907,1746909,1746910,1746912
  derivatives: 1746914
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Wednesday, 07. February 2018 10:01 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746903/+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 1747069] Re: artful 4.13 i386 kernels crash after memory hotplug remove

[Colin Ian King]

Fixed in 4.14 with:

f7f99100d8d95dbcf09e0216a143211e79418b9f is the first bad commit
commit f7f99100d8d95dbcf09e0216a143211e79418b9f
Author: Pavel Tatashin 
Date:   Wed Nov 15 17:36:44 2017 -0800

mm: stop zeroing memory during allocation in vmemmap

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

Title:
  artful 4.13 i386 kernels crash after memory hotplug remove

Status in linux package in Ubuntu:
  In Progress

Bug description:
  It seems all of the artful 4.13 are crashing on i386 install when
  memory hotplug removal is attempted.  This crash occurs a few seconds
  after the removal.  I have done a gross bisect back to the first
  4.13.0-11 which is also affected.

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

[Ubuntu Kernel Bot]

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

apport-collect 1747909

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

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

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

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

** Tags added: artful

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

Title:
  4.13 kernel panic on kfree (security_sk_free)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm frequently facing this issue with Artful kernels 4.13:

  [ 1317.490018] general protection fault:  [#1] SMP NOPTI
  [ 1317.491099] Modules linked in: ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter nfsv3 nfs_acl nfs lockd grace fscache edac_mce_amd 
qemu_fw_cfg pata_acpi sunrpc ip_tables x_tables bridge stp llc virtio_scsi 
input_leds kvm_amd kvm irqbypass virtio_blk virtio_net mac_hid
  [ 1317.494814] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.13.0-32-generic 
#35-Ubuntu
  [ 1317.496199] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1317.497373] task: 98a1ad675d00 task.stack: a76dc18f8000
  [ 1317.498274] RIP: 0010:kfree+0x53/0x160
  [ 1317.498852] RSP: 0018:98a1bfd03768 EFLAGS: 00010207
  [ 1317.499620] RAX:  RBX: 2e6c61636974706f RCX: 
0006
  [ 1317.500665] RDX: 2ecc30d0 RSI: 00010080 RDI: 
6762
  [ 1317.501677] RBP: 98a1bfd03780 R08: 00025d80 R09: 
a3bbd839
  [ 1317.502704] R10: 00b97c9557a5d1c0 R11:  R12: 
98a1a8430800
  [ 1317.503736] R13: a37a3dbe R14: 98a1a8430800 R15: 
98a1a8430800
  [ 1317.504753] FS:  () GS:98a1bfd0() 
knlGS:
  [ 1317.505888] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1317.506736] CR2: 7fbf9c9254d0 CR3: 000413c0a000 CR4: 
000406e0
  [ 1317.507753] Call Trace:
  [ 1317.508168]  
  [ 1317.508534]  security_sk_free+0x3e/0x50
  [ 1317.509135]  __sk_destruct+0x108/0x190
  [ 1317.509711]  sk_destruct+0x20/0x30
  [ 1317.510254]  __sk_free+0x82/0xa0
  [ 1317.510771]  sk_free+0x19/0x20
  [ 1317.511267]  sock_put+0x14/0x20
  [ 1317.511763]  tcp_v4_rcv+0x94d/0x9d0
  [ 1317.512319]  ? virtio_pci_probe+0xd0/0x130
  [ 1317.513010]  ip_local_deliver_finish+0x5c/0x1f0
  [ 1317.513800]  ip_local_deliver+0x6f/0xe0
  [ 1317.514495]  ? ip_rcv_finish+0x410/0x410
  [ 1317.515440]  ip_rcv_finish+0x120/0x410
  [ 1317.516193]  ip_rcv+0x28c/0x3a0
  [ 1317.516944]  ? packet_rcv+0x44/0x440
  [ 1317.517635]  __netif_receive_skb_core+0x39a/0xaa0
  [ 1317.518503]  ? dev_queue_xmit+0x10/0x20
  [ 1317.519279]  ? br_dev_queue_push_xmit+0x7a/0x140 [bridge]
  [ 1317.520262]  __netif_receive_skb+0x18/0x60
  [ 1317.520941]  ? __netif_receive_skb+0x18/0x60
  [ 1317.521638]  netif_receive_skb_internal+0x3f/0x3f0
  [ 1317.522408]  netif_receive_skb+0x1c/0x70
  [ 1317.523021]  br_netif_receive_skb+0x34/0x50 [bridge]
  [ 1317.523771]  br_pass_frame_up+0xcd/0x150 [bridge]
  [ 1317.524478]  ? br_port_flags_change+0x20/0x20 [bridge]
  [ 1317.525236]  br_handle_frame_finish+0x125/0x540 [bridge]
  [ 1317.526020]  ? cpumask_next_and+0x2c/0x40
  [ 1317.526638]  ? br_handle_local_finish+0x40/0x40 [bridge]
  [ 1317.527423]  br_handle_frame+0x156/0x300 [bridge]
  [ 1317.528156]  ? csum_partial+0x11/0x20
  [ 1317.528725]  __netif_receive_skb_core+0x212/0xaa0
  [ 1317.529432]  ? skb_checksum+0x35/0x50
  [ 1317.530012]  ? skb_append_datato_frags+0x200/0x200
  [ 1317.530729]  ? reqsk_fastopen_remove+0x140/0x140
  [ 1317.531415]  __netif_receive_skb+0x18/0x60
  [ 1317.532037]  ? __netif_receive_skb+0x18/0x60
  [ 1317.532684]  netif_receive_skb_internal+0x3f/0x3f0
  [ 1317.533394]  ? dev_gro_receive+0x2dc/0x480
  [ 1317.534029]  napi_gro_receive+0xc2/0xe0
  [ 1317.534628]  receive_buf+0x218/0xf70 [virtio_net]
  [ 1317.535332]  ? vring_unmap_one+0x1b/0x80
  [ 1317.535931]  virtnet_poll+0x173/0x268 [virtio_net]
  [ 1317.536645]  net_rx_action+0x13b/0x380
  [ 1317.537224]  ? skb_recv_done+0x30/0x40 [virtio_net]
  [ 1317.537962]  __do_softirq+0xde/0x2a5
  [ 1317.538553]  irq_exit+0xb6/0xc0
  [ 1317.539056]  do_IRQ+0x80/0xd0
  [ 1317.539530]  common_interrupt+0x1af/0x1af
  [ 1317.540139]  
  [ 1317.540500] RIP: 0010:native_safe_halt+0x6/0x10
  [ 1317.541178] RSP: 0018:a76dc18fbe70 EFLAGS: 0246 ORIG_RAX: 
ff8d
  [ 1317.542262] RAX:  RBX: 98a1ad675d00 RCX: 

  [ 1317.543302] RDX:  RSI:  RDI: