[Kernel-packages] [Bug 1722299] Re: linux: 4.4.0-98.121 -proposed tracker

2017-10-18 Thread Taihsiang Ho
Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/snap-certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  linux: 4.4.0-98.121 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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 snap-certification-testing series:
  In Progress
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1722301,1722302
  derivatives: 1722303,1722304,1722306,1722308,1722310
  -- 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/1722299/+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 1722299] Re: linux: 4.4.0-98.121 -proposed tracker

2017-10-18 Thread Taihsiang Ho
Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  linux: 4.4.0-98.121 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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 snap-certification-testing series:
  In Progress
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1722301,1722302
  derivatives: 1722303,1722304,1722306,1722308,1722310
  -- 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/1722299/+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 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

2017-10-18 Thread Kai-Heng Feng
It should be fixed with next Artful kernel 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/1724317

Title:
  Shutdown hangs / no standby - possible Wifi-bug in the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Shutdown-process hangs. After about two minutes the following
  message is displayed:

  Oct 17 18:47:06 Kahlan kernel: [  363.170588] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:47:06 Kahlan kernel: [  363.170592]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:47:06 Kahlan kernel: [  363.170593] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  Two Minutes later this message is displayed:
  Oct 17 18:49:07 Kahlan kernel: [  484.008650] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:49:07 Kahlan kernel: [  484.008659]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:49:07 Kahlan kernel: [  484.008662] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  This message repeates itself. If I am lucky, my laptop shuts down
  after some time.

  Also standby does not work. I think my wifi-adapter causes this
  problem.

  With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I
  found a bug report in the Arch Bug System
  (https://bugs.archlinux.org/task/55872

  In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the
  linuxkernel has a bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Oct 17 19:08:32 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962]
  InstallationDate: Installed on 2017-10-07 (10 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Acer Aspire VN7-571G
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Broadwell System
  dmi.product.name: Aspire VN7-571G
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  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/1724317/+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 1723644] Re: NetworkManager/wicd hang, might be driver issue

2017-10-18 Thread Kai-Heng Feng
It should be fixed with next Artful kernel 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/1723644

Title:
  NetworkManager/wicd hang, might be driver  issue

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Recently I had issues with NetworkManager. When I try to restart or close
  NetworkManager, the process hangs. First it sends a SIGTERM to the
  NetworkManager process, and after a while it sends SIGKILL, yet nothing
  happens. After the attempt to restart/close NetworkManager, the OS behaves
  badly:
  - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/
  SIGKILLing it causes the kill command to hang (no matter how many times I try
  it), it also hangs the terminal
  - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill
  command, can't close the terminal)
  - the OS won't reboot/suspend/shutdown (it does only after holding the restart
  button)

  Suspending/rebooting normally/shutdowning normally the laptop hangs the OS
  (because of NetworkManager).

  What I've tried:
  - reinstalling NetworkManager (uninstalling it using --purge, installing it 
clean)
  - deleting ~/.config
  - deleting ~/.cache
  - installing a version from NetworkManager from Debian (version: 1.8.4.2),
  reinstalling NetworkManager from Ubuntu back

   affects ubuntu
   affects ubuntu/network-manager
   affects ubuntu/systemd
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1259 F pulseaudio
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-15 (1 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IpRoute:
   default via 192.168.100.1 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.100.0/24 dev wlp3s0 proto kernel scope link src 192.168.100.6 metric 
600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57f3 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0489:e0a3 Foxconn / Hon Hai 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  Package: systemd
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1df26300-dc4d-42b3-bf5f-0c77c8df7667 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  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-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.29:bd07/21/2017:svnAcer:pnAspireE5-575G:pvrV1.29:rvnAcer:rnIronman_SK:rvrV1.29:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-575G
  dmi.product.version: V1.29
  dmi.sys.vendor: Acer
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Bojescu 2278c0fb-6947-469e-a8fc-7bbbafb10cf2  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp4s0f1  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:

[Kernel-packages] [Bug 237604] Re: Ctrl-key stuck in Gnome after continued browsing

2017-10-18 Thread Paras Avkirkar
** Changed in: linux (Ubuntu)
   Status: Invalid => 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/237604

Title:
  Ctrl-key stuck in Gnome after continued browsing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First of all - I have not been able to find a way to reproduce this
  bug when I want to. I have tried - a lot.

  That being said, this happens quite often. I use firefox 3 on Ubuntu
  8.04 and browse a lot using Ctrl+click (opening a new tab in the
  background) and Ctrl-W. At some time (often after 15-20 minutes) the
  control key seems stuck. Just normally clicking on any link opens the
  page in a background tab in firefox.

  Thought this might just affect firefox, but the whole desktop
  environment is affected, so I guess it must be gnome, somehow. The
  symptoms are very much like those described here:
  https://bugs.launchpad.net/bugs/194214

  Unfortunately I can't log out normally, because everything I click
  just seems highlighted. Can't type anything in thegnome- terminal;
  just have a rectangle where the letters should be. You can see the
  same thing when just pressing Ctrl in a normal session. I have to
  either Ctrl-Alt-F1 to a terminal and run "killall gnome-session" or
  kill the X-server via the Ctrl-Alt-Backspace combination.

  Because I have not found an easy way of reproducing this bug (quickly!) I 
guess it will be closed as incomplete, but since this has happened quite a few 
times since the launch of 8.04, I though I might report it.
  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory 
Controller Hub [8086:2a00] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:011b]
  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:011b]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/237604/+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 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

2017-10-18 Thread Kai-Heng Feng
I tried that in comment #58. It's already in linux-firmware.git.

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 
debugfs 1 tracing 1 dfs 0 testmode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 
bmi_id N/A crc32 6fc88fe7
  Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
  Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c
  Mar 04 18:28:34 ubuntu kernel: ath: EEPROM 

[Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic

2017-10-18 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Zesty)
   Status: Incomplete => 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/1723174

Title:
  Intel graphics problems on kernel 4.10.0-37-generic

Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in dkms source package in Zesty:
  New
Status in linux source package in Zesty:
  Invalid

Bug description:
  After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely 
slow.
  The reason is that i915 driver is UNCLAIMED now.

  Error from Xorg logs is:
  [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: 
Permission denied

  Environment:
  Ubuntu 17.04
  Kernel 4.10.0-37
  Intel HD Graphics 520
  INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1723174/+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 1723415] Re: ext4 filesystem does not use its badblock list

2017-10-18 Thread Dima
United, unified, multi-targeted, interactive and automotive bug-tracking
system is the most important thing the Universe should have.

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

Title:
  ext4 filesystem does not use its badblock list

Status in linux package in Ubuntu:
  Triaged

Bug description:
  1) Ubuntu 4.13.0-15.16-generic 4.13.4
  2) Will be attached.
  Always, when I have /dev/sdb2 mounted, I get an errors in the system log, 
such as in the file dmesg.txt (attached)(there are i/o errors and something).

  Thus I ran fsck:
  {
  root@user:~# fsck.ext4 -fck /dev/sdb2
  e2fsck 1.43.5 (04-Aug-2017)
  Checking for bad blocks (read-only test):   0.24% done, 0:25done  
   
  /dev/sdb2: Updating bad block inode.
  Pass 1: Checking inodes, blocks, and sizes
  Programming error?  block #230376 claimed for no reason in process_bad_block.
  Programming error?  block #230385 claimed for no reason in process_bad_block.
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  /dev/sdb2: * FILE SYSTEM WAS MODIFIED *
  }

  But the errors did not disappear and I ran "badblocks -so ./bads-sdb2.txt -b 
4096 /dev/sdb2"
  Then I tried "fsck.ext4 -l ./bads-sdb2.txt /dev/sdb2" and it showed, among 
other typical things, this:
  {
  Programming error?  block #230376 claimed for no reason in process_bad_block.
  Programming error?  block #230385 claimed for no reason in process_bad_block.
  }

  Then I ran "dump2fs -b /dev/sdb2" and found that every block from
  bads-sdb2.txt is already included in there, but the errors keep
  appear.

  And while I was searching for a solution, I found this:
  https://sourceforge.net/p/e2fsprogs/bugs/187/

  I think this situation can be found on Ubuntu 16.04 too.
  Thank you.

  1) Ubuntu Artful Aardvark (development branch) 17.10
  2) 4.13.0.15.16

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2193 F pulseaudio
   /dev/snd/controlC1:  user   2193 F pulseaudio
  CurrentDesktop: LXDE
  Date: Fri Oct 13 14:43:21 2017
  HibernationDevice: RESUME=UUID=726f52b2-474f-4c2d-b220-5db2446da453
  InstallationDate: Installed on 2017-10-06 (6 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-15-generic 
root=UUID=a0d2d217-37b4-4153-bb5c-c489bf5eb886 ro rootflags=subvol=@ quiet 
ipv6.disable=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: GA-880GM-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd10/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GM-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723415/+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 1723415] Re: ext4 filesystem does not use its badblock list

2017-10-18 Thread Dima
I did not use https://wiki.ubuntu.com/Bugs/Upstream/kernel, I just
filled what I could on bugzilla.kernel.org.
https://bugzilla.kernel.org/show_bug.cgi?id=197315

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

** Tags added: kernel-bug-reported-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/1723415

Title:
  ext4 filesystem does not use its badblock list

Status in linux package in Ubuntu:
  Triaged

Bug description:
  1) Ubuntu 4.13.0-15.16-generic 4.13.4
  2) Will be attached.
  Always, when I have /dev/sdb2 mounted, I get an errors in the system log, 
such as in the file dmesg.txt (attached)(there are i/o errors and something).

  Thus I ran fsck:
  {
  root@user:~# fsck.ext4 -fck /dev/sdb2
  e2fsck 1.43.5 (04-Aug-2017)
  Checking for bad blocks (read-only test):   0.24% done, 0:25done  
   
  /dev/sdb2: Updating bad block inode.
  Pass 1: Checking inodes, blocks, and sizes
  Programming error?  block #230376 claimed for no reason in process_bad_block.
  Programming error?  block #230385 claimed for no reason in process_bad_block.
  Pass 2: Checking directory structure
  Pass 3: Checking directory connectivity
  Pass 4: Checking reference counts
  Pass 5: Checking group summary information

  /dev/sdb2: * FILE SYSTEM WAS MODIFIED *
  }

  But the errors did not disappear and I ran "badblocks -so ./bads-sdb2.txt -b 
4096 /dev/sdb2"
  Then I tried "fsck.ext4 -l ./bads-sdb2.txt /dev/sdb2" and it showed, among 
other typical things, this:
  {
  Programming error?  block #230376 claimed for no reason in process_bad_block.
  Programming error?  block #230385 claimed for no reason in process_bad_block.
  }

  Then I ran "dump2fs -b /dev/sdb2" and found that every block from
  bads-sdb2.txt is already included in there, but the errors keep
  appear.

  And while I was searching for a solution, I found this:
  https://sourceforge.net/p/e2fsprogs/bugs/187/

  I think this situation can be found on Ubuntu 16.04 too.
  Thank you.

  1) Ubuntu Artful Aardvark (development branch) 17.10
  2) 4.13.0.15.16

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2193 F pulseaudio
   /dev/snd/controlC1:  user   2193 F pulseaudio
  CurrentDesktop: LXDE
  Date: Fri Oct 13 14:43:21 2017
  HibernationDevice: RESUME=UUID=726f52b2-474f-4c2d-b220-5db2446da453
  InstallationDate: Installed on 2017-10-06 (6 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-15-generic 
root=UUID=a0d2d217-37b4-4153-bb5c-c489bf5eb886 ro rootflags=subvol=@ quiet 
ipv6.disable=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-15-generic N/A
   linux-backports-modules-4.13.0-15-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: GA-880GM-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd10/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GM-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

2017-10-18 Thread bugproxy
--- Comment From cha...@us.ibm.com 2017-10-18 20:11 EDT---
Hi Kleber,

Is the verification for Zesty (17.04) a requirement for a 16.04 SRU?
This is the first time Zesty has been mentioned in this bug. Thanks.

Hi Shriya,

If Kleber states we do need a verification on 17.04 as well, would you
be able to do it? Thanks.

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

Title:
  [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command
  results in call traces and system goes for reboot.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 ==
  Problem Description :
  =
   
  While running perftool - testsuite, the perf hw breakpoint fails and it 
result in call traces , hence system goes for reboot .

  Machine details :
  ==
  System : P9 , WSP , Bare metal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Install perf.
  2. git clone perftool-testsuite.
  https://github.com/rfmvh/perftool-testsuite
  3. Do make.
  4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: 
kspace address execution mem:0xc035c020:x (command exitcode + output 
regexp parsing
  and call trace is seen as system goes for reboot.

  Call traces :
  ===

  ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request 
for data at address 0xc135d3b8
  [1602513.518553] Faulting instruction address: 0xc02869bc
  [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1]
  [1602513.518782] SMP NR_CPUS=2048 
  [1602513.518784] NUMA 
  [1602513.518842] PowerNV
  [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv 
cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd 
at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci 
libahci
  [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic 
#24
  [1602513.519524] task: c000203968c42c00 task.stack: c00020396571
  [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: 
c0286990
  [1602513.519747] REGS: c000203965713a40 TRAP: 0300   Not tainted  
(4.10.0-22-generic)
  [1602513.519876] MSR: 90009033 
  [1602513.519889]   CR: 22002448  XER: 
  [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 
SOFTE: 1 
  [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 
c134af00 
  [1602513.520058] GPR04:  4ee50300 c000203965713d20 
c000203965713e00 
  [1602513.520058] GPR08:  c135d100  
c0b71020 
  [1602513.520058] GPR12: c0286990 c7b4f300  
 
  [1602513.520058] GPR16:    
 
  [1602513.520058] GPR20:    
0001 
  [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 
4ee50300 
  [1602513.520058] GPR28: c134af00  c03fee038800 
 
  [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90
  [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0
  [1602513.521481] Call Trace:
  [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 
(unreliable)
  [1602513.521655] [c000203965713d00] [c03f7348] 
proc_sys_call_handler+0x138/0x1c0
  [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70
  [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0
  [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110
  [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0
  [1602513.522243] Instruction dump:
  [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 
fbc1fff0 fbe1fff8 
  [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378  4be66da9 
6000 3d22fff0 
  [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]---
  [1602513.522657] 

  It goes for reboot :

  After booting to Ubuntu , I see series of call traces.

  Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0

  ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for 
data at address 0xc13ad438
  [ 3476.626422] Faulting instruction address: 0xc029a140
  [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 3476.626615] SMP NR_CPUS=2048 

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

2017-10-18 Thread Aswin Gigi
Sorry for the late reply but @io-mattia98, even hitting escape doesn't
do anything for me when the system freezes.

@kleber-souza the patch does work as expected but just that the system
hangs while restarting, but if you power if off and restart it works
again, which I assume is an issue with GRUB.

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1700657/+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 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

2017-10-18 Thread Tyler Hicks
I tested the linux kernel SRU in Xenial and Zesty using the following
linux package versions:

 - xenial: linux-image-4.4.0-98-generic 4.4.0-98.121
 - zesty: linux-image-4.10.0-38-generic 4.10.0-38.42

The linux kernel SRU testing was successful and followed what's
documented in the [Linux Kernel Test Case] section of this bug
description. The accompanying libseccomp SRU has not been accepted into
xenial-proposed yet so I was unable to test lp1567597-test.c (although I
could test with lp1567597-kernel-test.c), as documented in the
[libseccomp Test Case] section but that's not a problem as the lp1567597
-kernel-test.c program and kernel selftests are sufficient.


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

** Tags removed: verification-needed

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in libseccomp source package in Zesty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added 

[Kernel-packages] [Bug 1721676] Re: implement errno action logging in seccomp for strict mode with snaps

2017-10-18 Thread Tyler Hicks
I tested the linux kernel SRU in Xenial and Zesty using the following
linux package versions:

 - xenial: linux-image-4.4.0-98-generic 4.4.0-98.121
 - zesty: linux-image-4.10.0-38-generic 4.10.0-38.42

The linux kernel SRU testing was successful and followed what's
documented in the [Test Case] section of this bug description.

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty

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

Title:
  implement errno action logging in seccomp for strict mode with snaps

Status in Snappy:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to
  parse the logs, etc and make developing on snappy easier.

  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when
  blocking illegal system calls.

  [Impact]

  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
  have a more friendly strict mode. Such functionality has been merged
  upstream into 4.14-rc2.

  No libseccomp changes are needed at this time since snap-confine loads
  the BPF filter directly into the kernel without using libseccomp.

  [Test Case]

  Running the libseccomp "live" tests will exercise the kernel's seccomp
  enforcement and help to help catch any regressions. Note that on
  Artful, there's an existing test failure (20-live-
  basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Running the seccomp kernel selftests is also a great to exercise
  seccomp and the kernel patch set proposed for the SRU includes
  additional seccomp selftests. To build, enter into the root of the
  kernel source tree and build the seccomp test binary:

  $ make -C tools/testing/selftests TARGETS=seccomp

  Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or
  even copy it to a test machine and run it there. On Xenial, 54/54
  tests should pass and 58/58 should pass on Zesty.

  

  Now we can run a single test to verify that SECCOMP_RET_ERRNO is
  logged when the application opts into it. First, verify that "errno"
  is listed in the actions_logged sysctl:

  $ cat /proc/sys/kernel/seccomp/actions_logged
  kill trap errno trace log

  Now, build and run the test program:

  $ gcc -o lp1721676-kernel-test lp1721676-kernel-test.c
  $ ./lp1721676-kernel-test
  SUCCESS: getpid() failed as expected: Operation not permitted

  It should have generated a message like this in /var/log/syslog:

  kernel: [79338.804966] audit: type=1326 audit(1507259221.875:27):
  auid=1000 uid=1000 gid=1000 ses=5 pid=3091 comm="lp1721676-kerne"
  exe="/home/tyhicks/lp1721676-kernel-test" sig=0 arch=c03e
  syscall=39 compat=0 ip=0x7fb91829c499 code=0x5

  Disable errno logging in the sysctl:

  $ echo kill trap trace log | sudo tee /proc/sys/kernel/seccomp/actions_logged
  kill trap trace log

  Rerun the test program and ensure that nothing was logged this time.

  [Regression Potential]

  The kernel patches received a lot of review between Kees and some
  others interested in improved seccomp logging. I authored the patches
  and feel comfortable/confident with my backported versions. They do
  not change the behavior of seccomp logging by default but offer ways
  applications to opt into more logging and, on the flipside, ways for
  the administrator to quite any additional logging.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic

2017-10-18 Thread Marco
Had exactly same issue with i915 when upgrading from kernel 4.10.0-35 to 
4.10.0-37, and fixed it by running:
sudo apt install --reinstall i915-4.11.6-4.10.0-dkms

Thanks!!

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

Title:
  Intel graphics problems on kernel 4.10.0-37-generic

Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in dkms source package in Zesty:
  New
Status in linux source package in Zesty:
  Incomplete

Bug description:
  After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely 
slow.
  The reason is that i915 driver is UNCLAIMED now.

  Error from Xorg logs is:
  [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: 
Permission denied

  Environment:
  Ubuntu 17.04
  Kernel 4.10.0-37
  Intel HD Graphics 520
  INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1723174/+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 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)

2017-10-18 Thread Chatty
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  

[Kernel-packages] [Bug 1724362] Re: Not booting - 17.10 Beta 2

2017-10-18 Thread Paul Meredith
I just tried command

echo $XDG_SESSION_TYPE

and it returned
x11


So I would say no ?

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  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: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724362/+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 1724362] Re: Not booting - 17.10 Beta 2

2017-10-18 Thread Paul Meredith
I installed the upstream Kernel you advised and re-commented custom.conf
and booted up with the RC5 Kernel without issue.

Problem fixed ... thank you.

Does that mean i'm now using wayland ?

Thanks !!

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  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: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: 

[Kernel-packages] [Bug 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)

2017-10-18 Thread Chatty
The above log files have this time been taken with Ubuntu 17.10 nightly
20171017 and show the firmware bug with microcode still being revision
0x1f.

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

[Kernel-packages] [Bug 1724650] RfKill.txt

2017-10-18 Thread Chatty
apport information

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

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: 

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
 

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
 

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: 

[Kernel-packages] [Bug 1724650] ProcCpuinfo.txt

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

[Kernel-packages] [Bug 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)

2017-10-18 Thread Chatty
apport information

** Description changed:

  During boot the above message appears.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
+  /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
+ CasperVersion: 1.387
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 17.10
+ LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 10f1:1a63 Importek 
+  Bus 001 Device 003: ID 8087:07dc Intel Corp. 
+  Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Medion S6417 MD99651
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.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.13.0-16.19-generic 4.13.4
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-16-generic N/A
+  linux-backports-modules-4.13.0-16-generic  N/A
+  linux-firmware 1.169
+ Tags:  artful
+ Uname: Linux 4.13.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/10/2015
+ dmi.bios.vendor: INSYDE Corp.
+ dmi.bios.version: GOLF2.0_BD4.12R
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: Golf 2.0
+ dmi.board.vendor: Medion
+ dmi.board.version: Type2 - Board Version
+ dmi.chassis.asset.tag: Chassis Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Medion
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
+ dmi.product.family: Type1Family
+ dmi.product.name: S6417 MD99651
+ 

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1685 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1685 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724650/+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 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)

2017-10-18 Thread Chatty
The above logs were taken with Ubuntu 17.04 where TSC deadline enables
just fine even though the microcode revision is 0x1f as in 17.10 where
this revision causes problems which ought to be solved in revision 0x25.

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724650/+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 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport

2017-10-18 Thread Chris Glass
A bug has been filed upstream here:
https://bugs.freedesktop.org/show_bug.cgi?id=103351

** Bug watch added: freedesktop.org Bugzilla #103351
   https://bugs.freedesktop.org/show_bug.cgi?id=103351

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

Title:
  Ubuntu Desktop ISO fails to boot with nouveau on a displayport

Status in Release Notes for Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the latest daily artful image (/current as of 2017-01-14), the
  following occurs on a system with nVidia graphics (on my system, a
  GTX970) when connected to a 4k display over a displayport:
  https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2

  Steps to reproduce:
  - Download latest daily image, check checksums, burn to USB
  - Boot from USB.
  - Choose "Install Ubuntu" or "try ubuntu" at the menu.

  This happens on the livecd, but also upon ugrading the system from a
  previous daily with a different kernel: my "old" daily booted and
  installed fine with kernel 4.12.0-12, then failed with same error once
  dist-upgraded.

  On the faulty system I could test with, it seems to *only* happen over
  displayport/on a 4k screen (I don't own a non-4k displayport screen to
  test the 4k out).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+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 1724650] UdevDb.txt

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724650/+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 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)

2017-10-18 Thread Chatty
apport information

** Tags added: apport-collected zesty

** Description changed:

  During boot the above message appears.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  Cannot stat file /proc/2447/fd/17: Stale file handle
+  Cannot stat file /proc/2447/fd/18: Stale file handle
+   USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
+  /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
+ CasperVersion: 1.380
+ CurrentDesktop: Unity:Unity7
+ DistroRelease: Ubuntu 17.04
+ LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 10f1:1a63 Importek 
+  Bus 001 Device 003: ID 8087:07dc Intel Corp. 
+  Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Medion S6417 MD99651
+ 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.10.0-19.21-generic 4.10.8
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-19-generic N/A
+  linux-backports-modules-4.10.0-19-generic  N/A
+  linux-firmware 1.164
+ Tags:  zesty
+ Uname: Linux 4.10.0-19-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/10/2015
+ dmi.bios.vendor: INSYDE Corp.
+ dmi.bios.version: GOLF2.0_BD4.12R
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: Golf 2.0
+ dmi.board.vendor: Medion
+ dmi.board.version: Type2 - Board Version
+ dmi.chassis.asset.tag: Chassis Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Medion
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
+ dmi.product.name: S6417 MD99651
+ dmi.product.version: TBD by OEM
+ dmi.sys.vendor: Medion

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread Chatty
apport information

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2447/fd/17: Stale file handle
   Cannot stat file /proc/2447/fd/18: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2325 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2325 F pulseaudio
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 10f1:1a63 Importek 
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Medion S6417 MD99651
  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.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/10/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: GOLF2.0_BD4.12R
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Golf 2.0
  dmi.board.vendor: Medion
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrGOLF2.0_BD4.12R:bd08/10/2015:svnMedion:pnS6417MD99651:pvrTBDbyOEM:rvnMedion:rnGolf2.0:rvrType2-BoardVersion:cvnMedion:ct10:cvrChassisVersion:
  dmi.product.name: S6417 MD99651
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Medion

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

2017-10-18 Thread bugproxy
--- Comment From bren...@br.ibm.com 2017-10-18 16:20 EDT---
Joseph, Mauricio,

We would like to have this fix in the next SRU. This is causing a lot of
impact on 16.04 HWE kernel users on POWER9.

Joseph, what is the last date we should submit this fix for the next
SRU?

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issuenext

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

Bug description:
  
  == SRU Justification ==
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The fix is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is commit 5080332c2c89 from linux-next which then
  emulates the instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  Commit ccd3cd361341 is needed as a prereq for Artful.
  Commits a3d96f70c147 and ccd3cd361341 are needed as prereqs for Zesty.

  == Fixes ==
  a3d96f70c147 ("powerpc/64s: Fix system reset vs general interrupt reentrancy")
  ccd3cd361341 ("powerpc/mce: Move 64-bit machine check code into mce.c")
  5080332c2c89 ("powerpc/64s: Add workaround for P9 vector CI load issue")

  == Regression Potential ==
  These commits are specific to powerpc.  They required some back porting but
   have been tested by IBM.


  -- Problem Description --

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

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

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

apport-collect 1724650

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724650/+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 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)

2017-10-18 Thread Sebastien Bacher
that doesn't seem a bug with evince the pdf reader?

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

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

Title:
  [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
  microcode to version: 0x25 (or later)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot the above message appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.25.92-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 20:25:20 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724650/+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 1724650] [NEW] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)

2017-10-18 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

During boot the above message appears.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.25.92-1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 18 20:25:20 2017
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful
-- 
[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to 
version: 0x25 (or later)
https://bugs.launchpad.net/bugs/1724650
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1724668] [NEW] Artful update to v4.13.7 stable release

2017-10-18 Thread 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.13.7 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.13.7 stable release shall be
applied:

watchdog: Revert "iTCO_wdt: all versions count down twice"
Linux 4.13.7

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

waitid(): Add missing access_ok() checks

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

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


** Tags: kernel-stable-tracking-bug

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

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

** 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.13.7 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 form of that patch. The v4.13.7 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.13.7 stable release shall be
+ applied:
  
-The following patches from the v4.13.7 stable release shall be
+ watchdog: Revert "iTCO_wdt: all versions count down twice"
+ Linux 4.13.7
+ 
+    The following patches from the v4.13.7 stable release shall be
  applied:
+ 
+ waitid(): Add missing access_ok() checks

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

** Changed in: linux (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Artful update to v4.13.7 stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  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.13.7 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.13.7 stable release shall be
  applied:

  watchdog: Revert "iTCO_wdt: all versions count down twice"
  Linux 4.13.7

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

  waitid(): Add missing access_ok() checks

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

2017-10-18 Thread 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.13.8 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.13.8 stable release shall be
applied:

USB: dummy-hcd: Fix deadlock caused by disconnect detection
MIPS: math-emu: Remove pr_err() calls from fpu_emu()
MIPS: bpf: Fix uninitialised target compiler error
mei: always use domain runtime pm callbacks.
dmaengine: edma: Align the memcpy acnt array size with the transfer
dmaengine: ti-dma-crossbar: Fix possible race condition with dma_inuse
NFS: Fix uninitialized rpc_wait_queue
nfs/filelayout: fix oops when freeing filelayout segment
HID: usbhid: fix out-of-bounds bug
crypto: skcipher - Fix crash on zero-length input
crypto: shash - Fix zero-length shash ahash digest crash
KVM: MMU: always terminate page walks at level 1
KVM: nVMX: fix guest CR4 loading when emulating L2 to L1 exit
usb: renesas_usbhs: Fix DMAC sequence for receiving zero-length packet
pinctrl/amd: Fix build dependency on pinmux code
iommu/amd: Finish TLB flush in amd_iommu_unmap()
device property: Track owner device of device property
Revert "vmalloc: back off when the current task is killed"
fs/mpage.c: fix mpage_writepage() for pages with buffers
ALSA: usb-audio: Kill stray URB at exiting
ALSA: seq: Fix use-after-free at creating a port
ALSA: seq: Fix copy_from_user() call inside lock
ALSA: caiaq: Fix stray URB at probe error path
ALSA: line6: Fix NULL dereference at podhd_disconnect()
ALSA: line6: Fix missing initialization before error path
ALSA: line6: Fix leftover URB at error-path during probe
drm/atomic: Unref duplicated drm_atomic_state in drm_atomic_helper_resume()
drm/i915/edp: Get the Panel Power Off timestamp after panel is off
drm/i915: Read timings from the correct transcoder in intel_crtc_mode_get()
drm/i915/bios: parse DDI ports also for CHV for HDMI DDC pin and DP AUX channel
drm/i915: Use crtc_state_is_legacy_gamma in intel_color_check
usb: gadget: configfs: Fix memory leak of interface directory data
usb: gadget: composite: Fix use-after-free in usb_composite_overwrite_options
PCI: aardvark: Move to struct pci_host_bridge IRQ mapping functions
Revert "PCI: tegra: Do not allocate MSI target memory"
direct-io: Prevent NULL pointer access in submit_page_section
fix unbalanced page refcounting in bio_map_user_iov
more bio_map_user_iov() leak fixes
bio_copy_user_iov(): don't ignore ->iov_offset
perf script: Add missing separator for "-F ip,brstack" (and brstackoff)
genirq/cpuhotplug: Enforce affinity setting on startup of managed irqs
genirq/cpuhotplug: Add sanity check for effective affinity mask
USB: serial: ftdi_sio: add id for Cypress WICED dev board
USB: serial: cp210x: fix partnum regression
USB: serial: cp210x: add support for ELV TFD500
USB: serial: option: add support for TP-Link LTE module
USB: serial: qcserial: add Dell DW5818, DW5819
USB: serial: console: fix use-after-free on disconnect
USB: serial: console: fix use-after-free after failed setup
RAS/CEC: Use the right length for "cec_disable"
x86/microcode: Do the family check first
x86/alternatives: Fix alt_max_short macro to really be a max()
KVM: nVMX: update last_nonleaf_level when initializing nested EPT
Linux 4.13.8

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

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


** Tags: kernel-stable-tracking-bug

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

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

** 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.13.8 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 form of that patch. The v4.13.8 

[Kernel-packages] [Bug 1724362] Re: Not booting - 17.10 Beta 2

2017-10-18 Thread Seth Forshee
Thanks. Unfortunately I don't see any errors or other useful information
about the problem in kern.log either.

Could you test the latest upstream kernel so we'll know whether or not
the problem has already been fixed? Currently this is 4.14-rc5, which
can be downloaded here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5/

You'll need the linux-image-*-generic package for amd64, and if you're
using any dkms packages you may also want to install the headers
packages (the one with generic in the name and the one that ends in
_all.deb). Thanks!

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  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: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724362/+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 1668105] Re: xhci_hcd module turns off usb host controller on boot

2017-10-18 Thread Nicolas Anquetil
+1
Having the same problems here :-(

Solution in post #6 and post #28 are not working

Symptoms: Mac working with normally with ubuntu 17.04
It seems that when I plugin one usb mouse I have at home this f*up the system 
and I can no longer use the mouse, trackpad, keyboard :-(
System is running as I can ssh to it from another computer.
Rebooting ubuntu does not help. Actually the system cannot shutdown properly, I 
have to turn it off (long press on the power button)
updated to kernel image 4.12 to no avail

Problem might also be due to putting the computer to sleep (I read
somewhere that it was not flawless on my mac, but I use suspend a lot)

I found different posts on the web reporting various USB problems (with camera, 
drive, etc)
But no solution yet

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

Title:
  xhci_hcd module turns off usb host controller on boot

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

Bug description:
  So we know this xhci_kcd was always shit in that it turns off the
  console usb keyboard for long running computers and that it on abrupt
  termination of Linux puts usb in a 12x slower mode. It is buggy, it
  was always buggy, and its getting worse.

  With Linux 4.8.0-37, this crappy software decides to halt the host
  controller on boot, ie. turn off the console keyboard preventing any
  boot. I cannot think of any situation where anyone would want their
  host controller halted.

  This is MacBook Pro 2015. So, it's already broken in UEFI-grub as it
  always was, ie. every key press takes 8 seconds, but you only need
  two, so you can boot in 16 s.

  I tried to disable the xhci_kcd crap by using kernel parameter
  noxhci_port_switch or modprobe.blacklist=xhci_hcd neither which works.

  Because it has crap in UEFI, the computer will not boot any external
  hard drive or usb fob. The only thing that works is Apple rescue that
  gets rid of the xhci garbage, and the boot os x immediately after
  that.

  So the log output
  xhci_hcd :00:14.0: Timeout while waiting for setup device command
  xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command.
  - and a bit later:
  xhci_hcd :00:14.0: Assuming host is dying, halting host.
  xhci_hcd :00:14.0: HC died; cleaning up

  This clown programming of Linux has to stop. Why would anyone ever want their 
host controller halted?
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  foxyboy5662 F pulseaudio
   /dev/snd/controlC0:  foxyboy5662 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=/dev/mapper/C89-SWAP
  MachineType: Apple Inc. MacBookPro12,1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=/dev/mapper/C89-RFS ro i915.enable_rc6=0
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-39-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (108 days ago)
  UserGroups: adm docker libvirt libvirtd sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1668105/+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 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-18 Thread Ian Bruntlett
Hi Joseph,

On 18 October 2017 at 19:47, Joseph Salisbury  wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>

I received an e-mail from qatrac...@stgraber.org with a subject of "A new
build of Lubuntu Alternate i386 is ready for testing!" - referring to
version: 20171017.1, with a link to  http://iso.qa.ubuntu.com/qatra
cker/milestones/383/builds/159145/testcases

This was downloaded by me:-
ian@turing:~/isos/2017-10-17.1$ md5sum artful-alternate-i386.iso
6beffce30b77f7c8105bde2c4e4d69b8  artful-alternate-i386.iso

I created install media by running Startup Disc Creator and the above
iso.

Booted my Samsung NC10 and installed the lubuntu 32-bit version. During
installation, everything was text mode and O.K. On booting into the system,
as soon as it switched from text mode to graphics mode, I experienced this
graphics corruption:-

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

I'm exhausted. I'll do those further tests tomorrow evening.

BW,


Ian

-- 
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page - https://sites.google.com/site/
ianbruntlett/home/free-software

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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


[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

2017-10-18 Thread s.illes79
anyone tried this from dell.com?
https://www.dell.com/support/article/uk/en/ukbsdt1/sln306440/killer-n1535-wireless-firmware-manual-update-guide-for-ubuntu-systems?lang=en

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 
debugfs 1 tracing 1 dfs 0 testmode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 
bmi_id N/A crc32 6fc88fe7
  Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
  

[Kernel-packages] [Bug 1716483] Re: [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0

2017-10-18 Thread dann frazier
I verified that the kdump failure symptom (Comment #3) has now been
resolved. The crashkernel successfully boots into userspace and is able
to complete the dump collection.

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  [SRU][Zesty] Fix lscpu segfault on ARM64 with SMBIOS v2.0

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  On ARM64 systems with smbios v2.0, lscpu segfaults. This is caused by the 
fact that lspci issues a read() on /dev/mem at the offset where it expects to 
find the SMBIOS structure array. However, this
  region is classified as EFI_RUNTIME_SERVICE_DATA (as per the UEFI spec), and 
so it is omitted from the linear mapping.

  [Test]
  The issue was observed with kexec/kdump usecases when a FPDT ACPI table is 
presented to HLOS from the firmware.

  [Fix]
  Fixed upstream:
  1151f838cb62 arm64: kernel: restrict /dev/mem read() calls to linear region

  [Regression Potential]
  The patch is confined to ARM64 arch, and applies only to systems with SMBIOS 
v2.0. Risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716483/+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 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-18 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1724639

** Tags added: iso-testing

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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


[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

2017-10-18 Thread F. H.
I installed this kernel on my Ubuntu 17.10 Arful Awkward, but it does not seem 
to work since kernel 4.10 is too old for my Lenovo Yoga 720-15.
(Link: 
https://launchpad.net/ubuntu/zesty/amd64/linux-image-4.10.0-38-generic/4.10.0-38.42
 )


Could you please publish a kernel 4.13 for artful, since it should be released 
tomorrow anyway?

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1700657/+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 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

2017-10-18 Thread Brian Murray
** No longer affects: ubuntu

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

Title:
  Shutdown hangs / no standby - possible Wifi-bug in the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Shutdown-process hangs. After about two minutes the following
  message is displayed:

  Oct 17 18:47:06 Kahlan kernel: [  363.170588] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:47:06 Kahlan kernel: [  363.170592]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:47:06 Kahlan kernel: [  363.170593] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  Two Minutes later this message is displayed:
  Oct 17 18:49:07 Kahlan kernel: [  484.008650] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:49:07 Kahlan kernel: [  484.008659]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:49:07 Kahlan kernel: [  484.008662] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  This message repeates itself. If I am lucky, my laptop shuts down
  after some time.

  Also standby does not work. I think my wifi-adapter causes this
  problem.

  With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I
  found a bug report in the Arch Bug System
  (https://bugs.archlinux.org/task/55872

  In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the
  linuxkernel has a bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Oct 17 19:08:32 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962]
  InstallationDate: Installed on 2017-10-07 (10 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Acer Aspire VN7-571G
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Broadwell System
  dmi.product.name: Aspire VN7-571G
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  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/1724317/+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 1724362] Re: Not booting - 17.10 Beta 2

2017-10-18 Thread Paul Meredith
Hi Seth,

Thanks for coming back to me on this issue.

And you are spot on I made the change to custom.conf you mentioned above
and it has booted straight up into Ubuntu looking normal again.

I have attached kern.log file...  please excuse all the BTRFS errors in
there i'm having issues with a corrupt drive at the minute as well.

Let me know if there is anything else I can help with.

Thanks

Paul


** Attachment added: "Kern.log file"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724362/+attachment/4975181/+files/kern.log

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  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: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724362/+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 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-18 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5

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

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

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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


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

2017-10-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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


[Kernel-packages] [Bug 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-18 Thread Ian Bruntlett
Here is a photo of the problem.

** Attachment added: "Here is a photo of the problem."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+attachment/4975110/+files/Display-problem.JPG

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  New

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

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

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

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

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


[Kernel-packages] [Bug 1724635] Re: linux-azure-edge: 4.13.0-1002.2 -proposed tracker

2017-10-18 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.13.0-1002.2 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-stable-phase-changed:Wednesday, 18. October 2017 18:01 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 4.13.0-1002.2 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-stable-phase-changed:Wednesday, 18. October 2017 18:01 UTC
  kernel-stable-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/1724635

Title:
  linux-azure-edge: 4.13.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow 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 package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.13.0-1002.2 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-stable-phase-changed:Wednesday, 18. October 2017 18:01 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

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

2017-10-18 Thread Brad Figg
** Description changed:

  This bug is for tracking the 3.13.0-135.184 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
  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/1724500

Title:
  linux: 3.13.0-135.184 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-135.184 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
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724500/+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 1724639] [NEW] Graphics problem - 80% of the Left hand side of screen solid black

2017-10-18 Thread Ian Bruntlett
Public bug reported:

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

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

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

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


** Tags: apport-bug artful i386

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  New

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 

[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )

2017-10-18 Thread Trent Nelson
Sorry, I missed Robie's comment yesterday.  Upstream seems
inactive/dead.  Nothing from Lennart on
https://bugs.freedesktop.org/buglist.cgi?product=libatasmart since 2011.
No commits to http://git.0pointer.net/libatasmart.git since 2012.  I
didn't see any indication the development had been picked up anywhere
else.

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  In Progress
Status in libatasmart source package in Trusty:
  New
Status in libatasmart source package in Xenial:
  New
Status in libatasmart source package in Yakkety:
  New

Bug description:
  Hello, here's my system info

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

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1581594/+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 1658733] Adds "noirqdistrib" parameter to kdump command line

2017-10-18 Thread bugproxy
--- Comment on attachment From maur...@br.ibm.com 2017-01-23 12:10 
EDT---


This patch fixes the issue. The noirqdistrib is a necessary parameter for ppc64 
platform as stated in kdump docs 
https://www.kernel.org/doc//Documentation/kdump/kdump.txt
With this fix crash kernel uses the correct irq server for the case where only 
one cpu is online.

** Attachment added: "Adds "noirqdistrib" parameter to kdump command line"
   
https://bugs.launchpad.net/bugs/1658733/+attachment/4975065/+files/add_noirqdistrib_param_for_ppc64.diff

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory 

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

2017-10-18 Thread Thadeu Lima de Souza Cascardo
** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache: write through
  [2.739122] sd 1:2:3:0: [sdl] Assuming drive cache: write through
  [2.739123] sd 1:2:2:0: [sdk] Assuming drive cache: write through
 

[Kernel-packages] [Bug 1720359] Re: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller

2017-10-18 Thread Eric Desrochers
** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty

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

Title:
  Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller

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

Bug description:
  Deploying ceph osd on Trusty/14.04 (LTS) with Ubuntu 4.4 series kernel
  on HP HW[1] system triggers "Controller lockup"[2]

  [1] - HW
  System Information
   Manufacturer: HP
   Product Name: ProLiant DL380 Gen9

  BIOS
    Vendor: HP
    Version: P89
    Release Date: 02/17/2017

  Smart Array Controller
   Smart Array P440 Controller

  [2] - /var/log/kern.log
  ...
  ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60
  eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60
  ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60
  hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30
  hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown 
abort service response 0x00
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359/+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 1698470] Re: [Zesty][Yakkety] rtl8192e bug fixes

2017-10-18 Thread cheltspy
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  The following commits needed to be added to the 4.10 and 4.4 kernels
  for stable operation of r8192e_pci driver. They are already in Xenial because 
  they came in with upstream stable updates.  However, upstream v4.10 is EOL so 
  these commits are being submitted via SRU request.

  All four commits are in mainline as of v4.12-rc2.

  == Fixes ==
  baabd567f87b ("staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out 
memory.")
  867510bde14e ("staging: rtl8192e: fix 2 byte alignment of register BSSIDR.")
  90be652c9f15 ("staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of 
EPROM_CMD.")
  95d93e271d92 ("staging: rtl8192e: GetTs Fix invalid TID 7 warning.")

  == Regression Potential ==
  These commits were also cc'd to stable and accepted, so additional upstream 
review
  was performed.

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


  
  The following commits needed to be added to 4.10 and 4.8 kernels for stable 
operation of r8192e_pci driver. They are already in 4.11 and in 4.4.

  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
   /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy1: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: N3700-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.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698470/+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 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

2017-10-18 Thread Thadeu Lima de Souza Cascardo
As this bug is about the use of noirqdistrib, this could affect other
targets besides multipath devices. So unmarking this as duplicate of the
multipath bug. Also, changing the title to indicate better what it is
about.

** This bug is no longer a duplicate of bug 1635597
   Ubuntu16.10:talclp1: Kdump failed with multipath disk

** Summary changed:

- Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root 
device
+ Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is 
missing as dump kernel parameter

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

** Changed in: makedumpfile (Ubuntu)
 Assignee: Louis Bouchard (louis) => Thadeu Lima de Souza Cascardo 
(cascardo)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > 

[Kernel-packages] [Bug 1724635] [NEW] linux-azure-edge: 4.13.0-1002.2 -proposed tracker

2017-10-18 Thread Marcelo Cerri
Public bug reported:

This bug is for tracking the 4.13.0-1002.2 upload package. This bug will
contain status and testing results related to that upload.

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

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

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

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

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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


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

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

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

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

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

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

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

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

** Changed in: kernel-sru-workflow/promote-to-updates
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru)

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

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

** Changed in: kernel-sru-workflow/security-signoff
   

[Kernel-packages] [Bug 1724614] Re: [KVM] Lower the default for halt_poll_ns to 200000 ns

2017-10-18 Thread Jorge Niedbalski
@jsalisbury,

Yes, I do plan to submit this as an SRU request to the kernel ML.

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

Title:
  [KVM] Lower the default for halt_poll_ns to 20 ns

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  [Environment]

  Reproducible <= 4.12 that means all our supported series + HWE
  (including edge).

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Linux 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  [Description]

  We've identified a constant high (~90%) system time load at the host level
  when a VCPU in a KVM guest remains or switches/resumes in/from halt/idle state
  in a constant frequency, usually for a slightly smaller time than the default 
polling
  period. 

  The halt polling mechanism has the intention to reduce latency in the cases 
  on which the guest is quickly resumed saving a call to the scheduler. 

  We've performed some testing by adjusting the 
/sys/module/kvm/parameters/halt_poll_ns 
  value which defines the max time that should be spend polling before calling 
the 
  scheduler to allow it to run other tasks (which defaults to 40 ns in 
Ubuntu). 

  With the default value the tests shows that the load remains nearly on 90% on 
a
  VCPU that has a single task in the run queue. 

  We've also tested altering the halt_poll_ns value to 20 ns and the results
  seems to drop the system time usage from 90% to ~25%.

  root@buneary:/home/ubuntu/trace# echo 20 > 
/sys/module/kvm/parameters/halt_poll_ns
  root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
  Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_ (56 CPU)

  02:33:59 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
  [...]
  02:34:03 PM 6 4.04 0.00 24.24 0.00 0.00 0.00 0.00 12.12 0.00 59.60
  02:34:04 PM 6 2.97 0.00 27.72 0.00 0.00 0.00 0.00 11.88 0.00 57.43
  Average: 6 2.45 0.00 25.97 0.00 0.00 0.00 0.00 12.07 0.00 59.51

  root@buneary:/home/ubuntu/trace# echo 40 > 
/sys/module/kvm/parameters/halt_poll_ns
  root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
  Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_ (56 CPU)

  02:34:08 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
  02:34:09 PM 6 1.94 0.00 92.23 0.00 0.00 0.00 0.00 3.88 0.00 1.94
  [...]
  Average: 6 1.38 0.00 89.74 0.00 0.00 0.00 0.00 7.30 0.00 1.58

  [Reproducer]

  1) Configure a KVM guest with a single pinned VCPU.
  2) Run the following program (http://pastebin.ubuntu.com/25731919/) at the 
KVM guest.
  $ gcc test.c -lpthread -o test && ./test 250 0
  3) Run mpstat at the host on the pinned CPU and compare the stats
  $ sudo mpstat 1 -P 6 5

  [Fix]

  Change the halt polling max time to half of the current value.

  In some fio benchmarks, halt_poll_ns=40 caused CPU utilization to
  increase heavily even in cases where the performance improvement was
  small.  In particular, bandwidth divided by CPU usage was as much as
  60% lower.

  To some extent this is the expected effect of the patch, and the
  additional CPU utilization is only visible when running the
  benchmarks.  However, halving the threshold also halves the extra
  CPU utilization (from +30-130% to +20-70%) and has no negative
  effect on performance.

  Signed-off-by: Paolo Bonzini 

  *
  
https://github.com/torvalds/linux/commit/b401ee0b85a53e89739ff68a5b1a0667d664afc9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724614/+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 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

2017-10-18 Thread Joseph Salisbury
Commit 2a8a98673c13 is in Xenial -proposed, kernel version:
Ubuntu-4.4.0-98.121.  It looks like you tested with version
4.4.0-62-generic.  Can you try testing with the -proposed Xenial kernel:

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.

Another option is to test with the current -updates Artful 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/1717224

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in kvm source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in kvm source package in Zesty:
  New
Status in linux source package in Zesty:
  In Progress
Status in procps source package in Zesty:
  New
Status in kvm source package in Artful:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 

[Kernel-packages] [Bug 1723644] Re: NetworkManager/wicd hang, might be driver issue

2017-10-18 Thread Mihai Bojescu
A few days have passed but my installation still has issues. It didn't
occur in Debian 9 or Debian Testing but it does in Ubuntu 17.10 and
Ubuntu 17.04. Strange.

As a workaround I'll use my phone as an external wireless network
adapter (connected through USB) so I can at least
suspend/reboot/shutdown my device normally.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

** Changed in: systemd (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/1723644

Title:
  NetworkManager/wicd hang, might be driver  issue

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Recently I had issues with NetworkManager. When I try to restart or close
  NetworkManager, the process hangs. First it sends a SIGTERM to the
  NetworkManager process, and after a while it sends SIGKILL, yet nothing
  happens. After the attempt to restart/close NetworkManager, the OS behaves
  badly:
  - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/
  SIGKILLing it causes the kill command to hang (no matter how many times I try
  it), it also hangs the terminal
  - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill
  command, can't close the terminal)
  - the OS won't reboot/suspend/shutdown (it does only after holding the restart
  button)

  Suspending/rebooting normally/shutdowning normally the laptop hangs the OS
  (because of NetworkManager).

  What I've tried:
  - reinstalling NetworkManager (uninstalling it using --purge, installing it 
clean)
  - deleting ~/.config
  - deleting ~/.cache
  - installing a version from NetworkManager from Debian (version: 1.8.4.2),
  reinstalling NetworkManager from Ubuntu back

   affects ubuntu
   affects ubuntu/network-manager
   affects ubuntu/systemd
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1259 F pulseaudio
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-15 (1 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IpRoute:
   default via 192.168.100.1 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.100.0/24 dev wlp3s0 proto kernel scope link src 192.168.100.6 metric 
600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57f3 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0489:e0a3 Foxconn / Hon Hai 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  Package: systemd
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1df26300-dc4d-42b3-bf5f-0c77c8df7667 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  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-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.29:bd07/21/2017:svnAcer:pnAspireE5-575G:pvrV1.29:rvnAcer:rnIronman_SK:rvrV1.29:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-575G
  dmi.product.version: V1.29
  dmi.sys.vendor: Acer
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Bojescu 2278c0fb-6947-469e-a8fc-7bbbafb10cf2  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp4s0f1  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   loloopback  unmanaged

[Kernel-packages] [Bug 1723644] Re: NetworkManager/wicd hang, might be driver issue

2017-10-18 Thread Mihai Bojescu
Hopefully it won't take long to fix...

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

Title:
  NetworkManager/wicd hang, might be driver  issue

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Recently I had issues with NetworkManager. When I try to restart or close
  NetworkManager, the process hangs. First it sends a SIGTERM to the
  NetworkManager process, and after a while it sends SIGKILL, yet nothing
  happens. After the attempt to restart/close NetworkManager, the OS behaves
  badly:
  - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/
  SIGKILLing it causes the kill command to hang (no matter how many times I try
  it), it also hangs the terminal
  - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill
  command, can't close the terminal)
  - the OS won't reboot/suspend/shutdown (it does only after holding the restart
  button)

  Suspending/rebooting normally/shutdowning normally the laptop hangs the OS
  (because of NetworkManager).

  What I've tried:
  - reinstalling NetworkManager (uninstalling it using --purge, installing it 
clean)
  - deleting ~/.config
  - deleting ~/.cache
  - installing a version from NetworkManager from Debian (version: 1.8.4.2),
  reinstalling NetworkManager from Ubuntu back

   affects ubuntu
   affects ubuntu/network-manager
   affects ubuntu/systemd
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1259 F pulseaudio
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-15 (1 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  IpRoute:
   default via 192.168.100.1 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.100.0/24 dev wlp3s0 proto kernel scope link src 192.168.100.6 metric 
600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57f3 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0489:e0a3 Foxconn / Hon Hai 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  Package: systemd
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1df26300-dc4d-42b3-bf5f-0c77c8df7667 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  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-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/21/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.29
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.29:bd07/21/2017:svnAcer:pnAspireE5-575G:pvrV1.29:rvnAcer:rnIronman_SK:rvrV1.29:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-575G
  dmi.product.version: V1.29
  dmi.sys.vendor: Acer
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Bojescu 2278c0fb-6947-469e-a8fc-7bbbafb10cf2  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp4s0f1  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1724562] Re: linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker

2017-10-18 Thread Brad Figg
** Description changed:

  This bug is for tracking the 3.13.0-135.184~precise1 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
  phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-135.184~precise1 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
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724562/+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 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic

2017-10-18 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: In Progress => Incomplete

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

** Also affects: dkms (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/1723174

Title:
  Intel graphics problems on kernel 4.10.0-37-generic

Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in dkms source package in Zesty:
  New
Status in linux source package in Zesty:
  Incomplete

Bug description:
  After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely 
slow.
  The reason is that i915 driver is UNCLAIMED now.

  Error from Xorg logs is:
  [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: 
Permission denied

  Environment:
  Ubuntu 17.04
  Kernel 4.10.0-37
  Intel HD Graphics 520
  INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1723174/+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 1721856] Re: Suspend ends after seconds and laptop resumes

2017-10-18 Thread Joseph Salisbury
The only .deb package you need to install is:
linux-image-4.12.0-041200-generic_4.12.0-041200.201710171537_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/1721856

Title:
  Suspend ends after seconds and laptop resumes

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  The suspend/standby ends after seconds and the laptop resumes like
  it'd wake up from suspend. I didn't use suspend for a long time
  (months or years) and can't even estimate when it worked for the last
  time.

  This issue is fixed in 4.14-rc3 mainline kernel - although some parts
  of the installation don't work, like ZFS and nvidia-340 which might
  cause the problem as well.

  I'm willing to do git bisect work if you confirm me that this makes
  sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18896 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Oct  6 20:21:35 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (664 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1724614] Re: [KVM] Lower the default for halt_poll_ns to 200000 ns

2017-10-18 Thread Joseph Salisbury
Do you plan on submitting an SRU request to the kernel team mailing
list?

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

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

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

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  [KVM] Lower the default for halt_poll_ns to 20 ns

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  [Environment]

  Reproducible <= 4.12 that means all our supported series + HWE
  (including edge).

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Linux 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  [Description]

  We've identified a constant high (~90%) system time load at the host level
  when a VCPU in a KVM guest remains or switches/resumes in/from halt/idle state
  in a constant frequency, usually for a slightly smaller time than the default 
polling
  period. 

  The halt polling mechanism has the intention to reduce latency in the cases 
  on which the guest is quickly resumed saving a call to the scheduler. 

  We've performed some testing by adjusting the 
/sys/module/kvm/parameters/halt_poll_ns 
  value which defines the max time that should be spend polling before calling 
the 
  scheduler to allow it to run other tasks (which defaults to 40 ns in 
Ubuntu). 

  With the default value the tests shows that the load remains nearly on 90% on 
a
  VCPU that has a single task in the run queue. 

  We've also tested altering the halt_poll_ns value to 20 ns and the results
  seems to drop the system time usage from 90% to ~25%.

  root@buneary:/home/ubuntu/trace# echo 20 > 
/sys/module/kvm/parameters/halt_poll_ns
  root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
  Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_ (56 CPU)

  02:33:59 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
  [...]
  02:34:03 PM 6 4.04 0.00 24.24 0.00 0.00 0.00 0.00 12.12 0.00 59.60
  02:34:04 PM 6 2.97 0.00 27.72 0.00 0.00 0.00 0.00 11.88 0.00 57.43
  Average: 6 2.45 0.00 25.97 0.00 0.00 0.00 0.00 12.07 0.00 59.51

  root@buneary:/home/ubuntu/trace# echo 40 > 
/sys/module/kvm/parameters/halt_poll_ns
  root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
  Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_ (56 CPU)

  02:34:08 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
  02:34:09 PM 6 1.94 0.00 92.23 0.00 0.00 0.00 0.00 3.88 0.00 1.94
  [...]
  Average: 6 1.38 0.00 89.74 0.00 0.00 0.00 0.00 7.30 0.00 1.58

  [Reproducer]

  1) Configure a KVM guest with a single pinned VCPU.
  2) Run the following program (http://pastebin.ubuntu.com/25731919/) at the 
KVM guest.
  $ gcc test.c -lpthread -o test && ./test 250 0
  3) Run mpstat at the host on the pinned CPU and compare the stats
  $ sudo mpstat 1 -P 6 5

  [Fix]

  Change the halt polling max time to half of the current value.

  In some fio benchmarks, halt_poll_ns=40 caused CPU utilization to
  increase heavily even in cases where the performance improvement was
  small.  In particular, bandwidth divided by CPU usage was as much as
  60% lower.

  To some extent this is the expected effect of the patch, and the
  additional CPU utilization is only visible when running the
  benchmarks.  However, halving the threshold also halves the extra
  CPU utilization (from +30-130% to +20-70%) and has no negative
  effect on performance.

  Signed-off-by: Paolo Bonzini 

  *
  
https://github.com/torvalds/linux/commit/b401ee0b85a53e89739ff68a5b1a0667d664afc9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724614/+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 1724513] Re: Freezes when screen is locked or off (Lenovo Thinkpad L450)

2017-10-18 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.93

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

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

** Tags added: kernel-da-key

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

Title:
  Freezes when screen is locked or off (Lenovo Thinkpad L450)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have the feeling I reported this before but I can't find the
  original issue. I'm experiencing freezes almost every time the screen
  is locked, and sometimes even after the screen is off (but this
  happens much less often).

  I had this issue before, at some point it started to fail again, and
  now is back, currently using 4.4.0-97-lowlatency.

  I tried a mainline kernel 4.13.7-041307-lowlatency and so far is all
  working good, it even fixes another ongoing problem that I didn't
  have, then I started having again, etc.
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575334) and
  some other glitches when using the dock to connect to an external
  monitor, that sometimes wasn't undetected after suspend.

  The system feels much more stable with this kernel in general.

  1) # cat /proc/version_signature
  cat: /proc/version_signature: No such file or directory

  2) # sudo lspci -vnvn
  00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: Lenovo Broadwell-U Host Bridge -OPI [17aa:503c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U 
Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:503c]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot-), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Lenovo Wildcat Point-LP PCI Express Root 
Port [17aa:503c]
Capabilities: [a0] Power 

[Kernel-packages] [Bug 1724362] Re: Not booting - 17.10 Beta 2

2017-10-18 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags added: kernel-key

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  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: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724362/+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 1724564] Re: Cannot enter password to unlock encryption in 4.10

2017-10-18 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key

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

Title:
  Cannot enter password to unlock encryption in 4.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm unable to enter my password on the screen to unlock the disk
  during boot using kernels 4.10.0-35 and 4.10.0-37. Using the
  4.9.45-040945 mainline kernel seems to work fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724564/+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 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic

2017-10-18 Thread Emanuele Cisbani
But it should run automatically, not manually...

On Wed, 18 Oct 2017 at 08:11 Matt Robinson <1723...@bugs.launchpad.net>
wrote:

> As per the last comment by Emanuele Cisbani (cisba), I re-installed
> 4.10.0-37 (the original source of video problems with synaptic.
>
> Then did: sudo apt install --reinstall i915-4.11.6-4.10.0-dkms
>
> And the problem is now fixed. :-)
>
> I also ran the intel Graphics Update which didn't perform any actual
> updates - none needed,
>
> [SOLVED]
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1723174
>
> Title:
>   Intel graphics problems on kernel 4.10.0-37-generic
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Zesty:
>   In Progress
>
> Bug description:
>   After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works
> extremely slow.
>   The reason is that i915 driver is UNCLAIMED now.
>
>   Error from Xorg logs is:
>   [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version
> 1.4: Permission denied
>
>   Environment:
>   Ubuntu 17.04
>   Kernel 4.10.0-37
>   Intel HD Graphics 520
>   INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions
>
-- 
Emanuele
on the earth for a while
looking for enlightenment
listening to the inner teacher
about.me/emanuelecisbani
keybase.io/cisba

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

Title:
  Intel graphics problems on kernel 4.10.0-37-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely 
slow.
  The reason is that i915 driver is UNCLAIMED now.

  Error from Xorg logs is:
  [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: 
Permission denied

  Environment:
  Ubuntu 17.04
  Kernel 4.10.0-37
  Intel HD Graphics 520
  INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+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 1724614] [NEW] [KVM] Lower the default for halt_poll_ns to 200000 ns

2017-10-18 Thread Jorge Niedbalski
Public bug reported:

[Environment]

Reproducible <= 4.12 that means all our supported series + HWE
(including edge).

Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

Linux 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

[Description]

We've identified a constant high (~90%) system time load at the host level
when a VCPU in a KVM guest remains or switches/resumes in/from halt/idle state
in a constant frequency, usually for a slightly smaller time than the default 
polling
period. 

The halt polling mechanism has the intention to reduce latency in the cases 
on which the guest is quickly resumed saving a call to the scheduler. 

We've performed some testing by adjusting the 
/sys/module/kvm/parameters/halt_poll_ns 
value which defines the max time that should be spend polling before calling 
the 
scheduler to allow it to run other tasks (which defaults to 40 ns in 
Ubuntu). 

With the default value the tests shows that the load remains nearly on 90% on a
VCPU that has a single task in the run queue. 

We've also tested altering the halt_poll_ns value to 20 ns and the results
seems to drop the system time usage from 90% to ~25%.

root@buneary:/home/ubuntu/trace# echo 20 > 
/sys/module/kvm/parameters/halt_poll_ns
root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_   (56 CPU)

02:33:59 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
[...]
02:34:03 PM 6 4.04 0.00 24.24 0.00 0.00 0.00 0.00 12.12 0.00 59.60
02:34:04 PM 6 2.97 0.00 27.72 0.00 0.00 0.00 0.00 11.88 0.00 57.43
Average: 6 2.45 0.00 25.97 0.00 0.00 0.00 0.00 12.07 0.00 59.51

root@buneary:/home/ubuntu/trace# echo 40 > 
/sys/module/kvm/parameters/halt_poll_ns
root@buneary:/home/ubuntu/trace# sudo mpstat 1 -P 6 5
Linux 4.10.0-33-generic (buneary) 10/16/2017 _x86_64_   (56 CPU)

02:34:08 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
02:34:09 PM 6 1.94 0.00 92.23 0.00 0.00 0.00 0.00 3.88 0.00 1.94
[...]
Average: 6 1.38 0.00 89.74 0.00 0.00 0.00 0.00 7.30 0.00 1.58

[Reproducer]

1) Configure a KVM guest with a single pinned VCPU.
2) Run the following program (http://pastebin.ubuntu.com/25731919/) at the KVM 
guest.
$ gcc test.c -lpthread -o test && ./test 250 0
3) Run mpstat at the host on the pinned CPU and compare the stats
$ sudo mpstat 1 -P 6 5

[Fix]

Change the halt polling max time to half of the current value.

In some fio benchmarks, halt_poll_ns=40 caused CPU utilization to
increase heavily even in cases where the performance improvement was
small.  In particular, bandwidth divided by CPU usage was as much as
60% lower.

To some extent this is the expected effect of the patch, and the
additional CPU utilization is only visible when running the
benchmarks.  However, halving the threshold also halves the extra
CPU utilization (from +30-130% to +20-70%) and has no negative
effect on performance.

Signed-off-by: Paolo Bonzini 

*
https://github.com/torvalds/linux/commit/b401ee0b85a53e89739ff68a5b1a0667d664afc9

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


** Tags: sts

** Tags added: sts

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

Title:
  [KVM] Lower the default for halt_poll_ns to 20 ns

Status in linux package in Ubuntu:
  New

Bug description:
  [Environment]

  Reproducible <= 4.12 that means all our supported series + HWE
  (including edge).

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Linux 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  [Description]

  We've identified a constant high (~90%) system time load at the host level
  when a VCPU in a KVM guest remains or switches/resumes in/from halt/idle state
  in a constant frequency, usually for a slightly smaller time than the default 
polling
  period. 

  The halt polling mechanism has the intention to reduce latency in the cases 
  on which the guest is quickly resumed saving a call to the scheduler. 

  We've performed some testing by adjusting the 
/sys/module/kvm/parameters/halt_poll_ns 
  value which defines the max time that should be spend polling before calling 
the 
  scheduler to allow it to run other tasks (which defaults to 40 ns in 
Ubuntu). 

  With the default value the tests shows that the load remains nearly on 90% on 
a
  VCPU that has a single task in the run queue. 

  We've also tested altering the halt_poll_ns value to 20 ns and the results
  seems to drop the system time usage from 90% to ~25%.

  root@buneary:/home/ubuntu/trace# echo 20 > 
/sys/module/kvm/parameters/halt_poll_ns
  root@buneary:/home/ubuntu/trace# sudo mpstat 1 

[Kernel-packages] [Bug 1724612] [NEW] x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

2017-10-18 Thread Dan Streetman
Public bug reported:

An upstream commit added Intel cpu model/microcode checks to disable
TSC_DEADLINE due to cpu errata:

commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
Author: Peter Zijlstra 
Date:   Wed May 31 17:52:03 2017 +0200

x86/apic: Add TSC_DEADLINE quirk due to errata


That commit is included in the Ubuntu kernels starting at artful v4.13.  
However, the commit includes a check for Skylake Xeons, but the microcode 
update version number differs based on Skylake Xeon stepping, so an additional 
commit is required to correctly check the microcode level of both stepping 3 
and stepping 4 Skylake Xeons, and disable/enable TSC_DEADLINE appropriately.

Upstream commit that corrects the check is:

commit 616dd5872e52493863b0202632703eebd51243dc
Author: Len Brown 
Date:   Wed Oct 11 17:16:04 2017 -0400

x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping


Without the additional commit, Skylake Xeon stepping-3 cpus with the fixed 
microcode version will incorrectly have their TSC_DEADLINE disabled.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

Title:
  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

Status in linux package in Ubuntu:
  In Progress

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date:   Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  
  That commit is included in the Ubuntu kernels starting at artful v4.13.  
However, the commit includes a check for Skylake Xeons, but the microcode 
update version number differs based on Skylake Xeon stepping, so an additional 
commit is required to correctly check the microcode level of both stepping 3 
and stepping 4 Skylake Xeons, and disable/enable TSC_DEADLINE appropriately.

  Upstream commit that corrects the check is:

  commit 616dd5872e52493863b0202632703eebd51243dc
  Author: Len Brown 
  Date:   Wed Oct 11 17:16:04 2017 -0400

  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

  
  Without the additional commit, Skylake Xeon stepping-3 cpus with the fixed 
microcode version will incorrectly have their TSC_DEADLINE disabled.

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

2017-10-18 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => 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/1722299

Title:
  linux: 4.4.0-98.121 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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 snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1722301,1722302
  derivatives: 1722303,1722304,1722306,1722308,1722310
  -- 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/1722299/+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 1722306] Re: linux-aws: 4.4.0-1039.48 -proposed tracker

2017-10-18 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-certification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Canonical 
Hardware Certification (canonical-hw-cert)

** Changed in: kernel-sru-workflow/snap-release-to-edge
   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/1722306

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1722299
  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/1722306/+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 1722299] Re: linux: 4.4.0-98.121 -proposed tracker

2017-10-18 Thread Kleber Sacilotto de Souza
** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-certification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Canonical 
Hardware Certification (canonical-hw-cert)

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

Title:
  linux: 4.4.0-98.121 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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 snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1722301,1722302
  derivatives: 1722303,1722304,1722306,1722308,1722310
  -- 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/1722299/+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 1724162] Re: linux: -proposed tracker

2017-10-18 Thread Andy Whitcroft
** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in linux package in Ubuntu:
  Invalid

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

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

2017-10-18 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  linux: 3.13.0-135.184 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-135.184 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-sru-workflow/+bug/1724500/+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 1724562] Re: linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker

2017-10-18 Thread Andy Whitcroft
** Also affects: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Confirmed

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

Title:
  linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-135.184~precise1 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-sru-workflow/+bug/1724562/+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 1724562] Re: linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker

2017-10-18 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Description changed:

  This bug is for tracking the 3.13.0-135.184~precise1 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-stable-phase:Packaging
- kernel-stable-phase-changed:Wednesday, 18. October 2017 13:01 UTC
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 18. October 2017 13:31 UTC

** Description changed:

  This bug is for tracking the 3.13.0-135.184~precise1 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: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 18. October 2017 13:31 UTC
+ phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-135.184~precise1 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-sru-workflow/+bug/1724562/+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 1722336] Re: linux-lts-trusty: 3.13.0-134.183~precise1 -proposed tracker

2017-10-18 Thread Thadeu Lima de Souza Cascardo
*** This bug is a duplicate of bug 1724562 ***
https://bugs.launchpad.net/bugs/1724562

** This bug has been marked a duplicate of bug 1724562
   linux-lts-trusty: 3.13.0-135.184~precise1 -proposed tracker

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

Title:
  linux-lts-trusty: 3.13.0-134.183~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1722335
  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/1722336/+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 1724362] Re: Not booting - 17.10 Beta 2

2017-10-18 Thread Seth Forshee
Sounds like this is probably a problem in the graphics driver. When you
boot in recovery mode you're getting a reduced-functionality graphics
environment, which means that the logs that were attached don't show us
anything about what happens when you try to boot normally. Could you
attach the /var/log/kern.log file from your machine?

As a workaround, you could try forcing use of X instead of wayland. To
do this you need to edit /etc/gdm3/custom.conf and uncomment (i.e.
remove the # character) from the line which contains
"#WaylandEnable=false".

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

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  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: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

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

apport-collect 1724564

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

Title:
  Cannot enter password to unlock encryption in 4.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm unable to enter my password on the screen to unlock the disk
  during boot using kernels 4.10.0-35 and 4.10.0-37. Using the
  4.9.45-040945 mainline kernel seems to work fine.

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


  1   2   >