date:20180117

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/radeon

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

Title:
  Black screen with iMac 2011 and ATI Radeon 6970M

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear community!

  I have installed Ubuntu 17.10 (also tried 17.04 and 16.04), and the
  system gets a black screen on boot with all tested Ubuntu versions.
  Also ping and ssh to the host does not work. The fan's are running,
  the screen is black and nothing more.

  When i insert in Grub nomodeset, the system can boot.

  I have also tested Kernel 4.14 and 4.15RC7.

  Hardware Information:

  00:02.0 Display controller: Intel Corporation 2nd Generation Core
  Processor Family Integrated Graphics Controller (rev 09)

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Blackcomb [Radeon HD 6970M/6990M]

  
  Thanks for help or any hint.

  Best regards,

  Hans
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1756 F pulseaudio
   /dev/snd/controlC1:  christian   1756 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/storage-swap
  InstallationDate: Installed on 2018-01-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  MachineType: Apple Inc. iMac12,2
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=/dev/mapper/storage-root ro rootflags=subvol=@ nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM121.88Z.004D.B00.1708080012
  dmi.board.name: Mac-942B59F58194171B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac12,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B59F58194171B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,2:pvr1.0:rvnAppleInc.:rnMac-942B59F58194171B:rvriMac12,2:cvnAppleInc.:ct13:cvrMac-942B59F58194171B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1730150] Re: Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since upgrading from Ubuntu 17.04 to 17.10

2018-01-17 Thread Alan

Update

On learning that a Nautilus upgrade for Ubuntu is unlikely in the
forseeable future, today I installed gphoto2, gphotofs and gtkam on one
of my Ubuntu 17.10 computers, then re-tested the Fuji camera.

When the camera is connected to a USB port, no notification appears and no PTP 
camera device appears in the Nautilus side bar.
The output of lsusb displays the camera maker's name "Fuji Photo Film Co., Ltd" 
in the line relating to the camera's USB port.
Gtkam's "Add Camera" dialog can display the camera's make and model when 
clicking on the "Detect" button, but clicking the "OK" button gives a "Could 
not initialise camera" dialog.
The "gphoto2 --auto-detect" command generates the camera's make, model and USB 
port in its output.  However the commands "gphoto2 --summary", "gphoto2 
--list-files" and "gphoto2 --get-all-files" each return (in part):

"An error occurred in the io-library ('Unspecified error'): No error 
description available
 *** Error (-1: 'Unspecified error') ***".

As of today, Ubuntu 17.04 and Fedora 27 are still mounting and reading
the files on the camera correctly (Nautilus 3.20.4 and 3.26.4
respectively). Note the problem was observed in Fedora 26 but not in
Fedora 25

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

Title:
  Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since
  upgrading from Ubuntu 17.04 to 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  What happens:
  Something appears to have changed in Nautilus after Nautilus version 
1:3.20.4-0ubuntu2 (as in Ubuntu 17.04) and by version 1:3.26.0.0ubuntu1 (as in 
Ubuntu 17.10)*, causing the storage on my USB PTP camera (a Fujifilm HS30EXR) 
not to be visible to Nautilus when the camera is connected to the computer via 
USB and switched on.  (Camera firmware was updated and the camera retested on 
two Ubuntu 17.10 computers)

  What is expected to happen:
  On my remaining Ubuntu 17.04 computer (and earlier versions) the camera 
always pops up in the Nautilus left-hand sidebar when the camera is connected 
via USB and switched on.

  To reproduce the bug:
  1. Launch "Files" from the Dock
  2. Connect a Fujifilm HS30EXR camera (WITH an SD card installed) via USB
  3. Observe if camera can be browsed in Nautilus.

  What is still working:
  Three other cameras were tested and found not to have this problem with 
Nautilus: Acorn Ltl5310A (with SD card storage), Nikon P340 (SD card) and 
Olympus C8080WZ (xD and CF cards).

  More detail:
  Apport information report attached.

  Problem occurs when logged in to either Gnome or Unity Desktop in
  Ubuntu 17.10.

  On a prompt from an askubuntu.com user I also tested the Fuji camera
  on a Ubuntu 17.10 live USB (64 bit ISO downloaded 2 Nov 2017) and
  found the problem to occur there as well.

  Problems with Fuji cameras may have occurred in the past and been
  fixed - see Bug #1273498

  * Problem may have appeared on or before Nautilus version 3.24.2.1
  (Fedora WS 26), but was not observed in Fedora 25

  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alan   1376 F pulseaudio
   /dev/snd/controlC0:  alan   1376 F pulseaudio
   /dev/snd/controlC1:  alan   1376 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 11:33:43 2017
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=d20ac35f-b382-4cd9-8e3d-89b62ff15b02
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2017-02-09 (268 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=4f5ff60f-71fa-4354-8c46-85a532f5e205 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
  RfKill:
   
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   11:34:19.352: The udisks-daemon is running (name-owner :1.1).
  UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dm

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2018-01-17 Thread Matthew Senn

I have been having issues since my "new" laptop (Dell Latitude E5470)
arrived in April 2017.  I blamed it on being a refurb and being too lazy
to call and have it replaced during the warranty period.  I checked the
box to enable the pre-release updates, installed said updates and
haven't had an issue in almost two days -- i couldn't make it two
minutes prior.  I sure missed my BT keyboard and mouse!

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

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

2018-01-17 Thread bugproxy

--- Comment From shriy...@in.ibm.com 2018-01-18 00:36 EDT---
Hi ,
Can you please provide ppc64el packages , here I see 'amd' packages in the link 
mentioned above.

Ex : http://kernel.ubuntu.com/~jsalisbury/lp1743541/linux-
tools-4.13.0-17_4.13.0-17.20_amd64.deb

Thanks,
Shriya

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

Title:
  Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is
  offline

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-16 
04:58:48 ==
  Problem Description :
  =

  cpupower monitor fails to show stop states when cpu 0 is made offline.

  Testing :
  =
  root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# 

  root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop | stop | stop 
 0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.01

  Details :
  
  uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 
21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  OS : Ubuntu 18.04
  Machine : Witherspoon ( DD2.1) and Boston (DD.01)

  Patch :
  
  Patch that fixes the issue : 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  == Comment: #1 - VIPIN K. PARASHAR  - 2018-01-16 
05:09:40 ==
  (In reply to comment #0)

  > Patch :
  > 
  > Patch that fixes the issue :
  > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
  > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  $ git log dbdc468f35ee827 -1
  commit dbdc468f35ee827cab2753caa1c660bdb832243a
  Author: Abhishek Goel 
  Date:   Wed Nov 15 14:10:02 2017 +0530

  cpupower : Fix cpupower working when cpu0 is offline
  
  cpuidle_monitor used to assume that cpu0 is always online which is not
  a valid assumption on POWER machines. This patch fixes this by getting
  the cpu on which the current thread is running, instead of always using
  cpu0 for monitoring which may not be online.
  
  Signed-off-by: Abhishek Goel 
  Signed-off-by: Shuah Khan 
  $

  Commit dbdc468f3 is available with 4.15-rc2 onwards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1743541/+subscriptions

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

[Kernel-packages] [Bug 1743946] Missing required logs.

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 1743946

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: artful

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

Title:
  kexec reboot = NMI: PCI system error (SERR) for reason a1 on CPU 0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On 16.04 with linux-image-lowlatency-hwe-16.04 amd64 (currently
  4.13.0-30-lowlatency) with kexec-tools default-configured to handle
  reboots with the current kernel version (no GRUB detect) and
  /proc/cmdline.

  The system freezes either permanently (requiring a hard power-off) or
  for tens of seconds, showing (copied from a photograph):

  kexec_core: Starting new kernel
  nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
  NMI: PCI system error (SERR) for reason a1 on CPU 0.
  Dazed and confused, but trying to continue

  Due to the nature of the failure there is no additional logging or
  clues. I tried "nopti" in case recent 'Meltdown' changes were
  responsible but it still happens. I've only just enabled kexec on this
  system so have no historical indications of it having worked.

  System is Dell XPS M1530, Core 2 Duo T9300, 4GB RAM

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

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

[Kernel-packages] [Bug 1743946] [NEW] kexec reboot = NMI: PCI system error (SERR) for reason a1 on CPU 0

2018-01-17 Thread TJ

Public bug reported:

On 16.04 with linux-image-lowlatency-hwe-16.04 amd64 (currently
4.13.0-30-lowlatency) with kexec-tools default-configured to handle
reboots with the current kernel version (no GRUB detect) and
/proc/cmdline.

The system freezes either permanently (requiring a hard power-off) or
for tens of seconds, showing (copied from a photograph):

kexec_core: Starting new kernel
nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
NMI: PCI system error (SERR) for reason a1 on CPU 0.
Dazed and confused, but trying to continue

Due to the nature of the failure there is no additional logging or
clues. I tried "nopti" in case recent 'Meltdown' changes were
responsible but it still happens. I've only just enabled kexec on this
system so have no historical indications of it having worked.

System is Dell XPS M1530, Core 2 Duo T9300, 4GB RAM

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


** Tags: artful

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

Title:
  kexec reboot = NMI: PCI system error (SERR) for reason a1 on CPU 0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On 16.04 with linux-image-lowlatency-hwe-16.04 amd64 (currently
  4.13.0-30-lowlatency) with kexec-tools default-configured to handle
  reboots with the current kernel version (no GRUB detect) and
  /proc/cmdline.

  The system freezes either permanently (requiring a hard power-off) or
  for tens of seconds, showing (copied from a photograph):

  kexec_core: Starting new kernel
  nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
  NMI: PCI system error (SERR) for reason a1 on CPU 0.
  Dazed and confused, but trying to continue

  Due to the nature of the failure there is no additional logging or
  clues. I tried "nopti" in case recent 'Meltdown' changes were
  responsible but it still happens. I've only just enabled kexec on this
  system so have no historical indications of it having worked.

  System is Dell XPS M1530, Core 2 Duo T9300, 4GB RAM

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

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

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

2018-01-17 Thread Steve Langasek

Ubuntu 17.04 has reached end of life.  No further bugfixes will be
applied to this version.

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Won't 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/1709889

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Won't Fix

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other than the console,
  leaving

[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

2018-01-17 Thread clickwir

Tested on 4.15 rc8

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

Title:
  Screen blank, audio choppy, system locked

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1465.175694] INFO: NMI handler (perf_event_nmi_handler)

[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

2018-01-17 Thread clickwir

Installed 4.15 rc8 and same issue.

 dmesg 

[ 1265.953008] sched: RT throttling activated
[ 1265.953018] clocksource: timekeeping watchdog on CPU4: Marking clocksource 
'tsc' as unstable because the skew is too large:
[ 1265.953021] clocksource:   'hpet' wd_now: 38b37199 
wd_last: 3829ff32 mask: 
[ 1265.953022] clocksource:   'tsc' cs_now: 4262fdbe767 
cs_last: 425d7d7d680 mask: 
[ 1265.953023] tsc: Marking TSC unstable due to clocksource watchdog
[ 1265.953040] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
[ 1265.953041] sched_clock: Marking unstable (1265908240846, 
44771742)<-(1266267179035, -314139659)
[ 1275.809138] clocksource: Switched to clocksource hpet
[ 1299.951513] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
108.138 msecs
[ 1299.951516] perf: interrupt took too long (845222 > 2500), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1300.790347] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
137.277 msecs
[ 1300.790351] perf: interrupt took too long (1072756 > 1056527), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1306.558101] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
208.273 msecs
[ 1306.558101] perf: interrupt took too long (1627614 > 1340945), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1307.396931] hrtimer: interrupt took 629121891 ns
[ 1310.123102] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.705 msecs
[ 1323.540307] radeon :01:00.0: ring 0 stalled for more than 19176msec
[ 1323.540312] radeon :01:00.0: GPU lockup (current fence id 
0x00022c50 last fence id 0x00022c51 on ring 0)
[ 1323.540321] perf: interrupt took too long (2198839 > 2034517), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1337.804353] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.718 msecs
[ 1337.804353] perf: interrupt took too long (3803000 > 2748548), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1340.945936] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.758 msecs
[ 1342.623577] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
393.159 msecs
[ 1352.270069] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[kworker/u16:2:4609]
[ 1352.270071] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nfsv3 nfs_acl cfg80211 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace fscache zram binfmt_misc nls_iso8859_1 edac_mce_amd kvm_amd kvm 
irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi ghash_clmulni_intel 
pcbc snd_hda_intel input_leds snd_hda_codec snd_hda_core aesni_intel snd_hwdep 
snd_seq_midi aes_x86_64 snd_seq_midi_event crypto_simd glue_helper cryptd 
snd_rawmidi snd_ctxfi snd_seq snd_pcm wmi_bmof k10temp eeepc_wmi asus_wmi 
sparse_keymap video snd_seq_device fam15h_power snd_timer
[ 1352.270108]  i2c_piix4 snd soundcore shpchp mac_hid bonding parport_pc ppdev 
lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq 
hid_generic usbhid hid radeon i2c_algo_bit ttm e1000e drm_kms_helper 
syscopyarea sysfillrect ptp sysimgblt fb_sys_fops pps_core drm ahci r8169 
libahci mii wmi
[ 1352.270128] CPU: 2 PID: 4609 Comm: kworker/u16:2 Not tainted 
4.15.0-041500rc8-generic #201801142030
[ 1352.270129] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./M5A97 EVO, BIOS 1604 10/16/2012
[ 1352.270155] Workqueue: events_power_efficient radeon_fence_check_lockup 
[radeon]
[ 1352.270177] RIP: 0010:evergreen_is_display_hung+0x125/0x1b0 [radeon]
[ 1352.270178] RSP: 0018:9b94495ebda0 EFLAGS: 0286 ORIG_RAX: 
ff11
[ 1352.270180] RAX:  RBX: 0008 RCX: 0003
[ 1352.270181] RDX: 0003 RSI: 000112a0 RDI: 0005509f
[ 1352.270181] RBP: 9b94495ebdf8 R08:  R09: 
[ 1352.270182] R10:  R11: 0055 R12: 8c3596e8
[ 1352.270183] R13: 0001 R14: 003f R15: 0001
[ 1352.270184] FS:  () GS:8c35bec8() 
knlGS:
[ 1352.270185] CS:  0010 DS:  ES:  CR0: 80050033
[ 1352.270186] CR2: 7fb40fd82000 CR3: 00061d2dc000 CR4: 000406e0
[ 1352.270187] Call Trace:
[ 1352.270210]  evergreen_gpu_check_soft_reset+0xc5/0x120 [radeon]
[ 1352.270231]  evergreen_gfx_is_lockup+0x17/0x40 [radeon]
[ 1352.270246]  radeon_fence_check_lockup+0x92/0x170 [radeon]
[ 1352.270249]  process_one_work+0x1ea/0x410
[ 1352.270250]  worker_thread+0x253/0x410
[ 1352.270253]  kthread+0x11e/0x140
[ 1352.270254]  ? process_one_work+0x410/

[Kernel-packages] [Bug 1683760] Re: ETPS/2 Elantech Touchpad inconsistently detected (Lenovo Y700 15ISK)

Sounds like you run the command after the touchpad doesn't work.

What if you run the command right after boot?

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

Title:
  ETPS/2 Elantech Touchpad inconsistently detected (Lenovo Y700 15ISK)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has been happening reliably on my Lenovo Y700 15ISK since
  15.10... Sometimes it shows up as ETPS/2, sometimes PS/2, sometimes
  Logitech Wheelmouse... Most of the time it shows as "PS/2 Logitech
  Wheel Mouse" but none of the multitouch (2 finger scroll, 3 finger
  middle-click) can be set up. synclient says no device is present.

  This is likely related to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dphillips   1280 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 18 07:40:12 2017
  InstallationDate: Installed on 2017-04-18 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80NV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=8bba488a-b6df-4c29-8a90-8811c1078048 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN53WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN53WW:bd09/19/2016:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
  dmi.product.name: 80NV
  dmi.product.version: Lenovo ideapad Y700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1743872] Re: Not work 802.11ac WLAN Adapter

Seems like there's no in-tree driver support.

A quick google shows that `rtl8812au-dkms` might support it.
0bda:a811 is not in it's usb_device_id table, so you need to manually edit it.

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

Title:
  Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1683760] Re: ETPS/2 Elantech Touchpad inconsistently detected (Lenovo Y700 15ISK)

2018-01-17 Thread DevenPhillips

Not reliably. Sometimes it will fix things when they go wrong, but not
more than about 60%.

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

Title:
  ETPS/2 Elantech Touchpad inconsistently detected (Lenovo Y700 15ISK)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has been happening reliably on my Lenovo Y700 15ISK since
  15.10... Sometimes it shows up as ETPS/2, sometimes PS/2, sometimes
  Logitech Wheelmouse... Most of the time it shows as "PS/2 Logitech
  Wheel Mouse" but none of the multitouch (2 finger scroll, 3 finger
  middle-click) can be set up. synclient says no device is present.

  This is likely related to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dphillips   1280 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 18 07:40:12 2017
  InstallationDate: Installed on 2017-04-18 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80NV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=8bba488a-b6df-4c29-8a90-8811c1078048 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN53WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN53WW:bd09/19/2016:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
  dmi.product.name: 80NV
  dmi.product.version: Lenovo ideapad Y700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1683760] Re: ETPS/2 Elantech Touchpad inconsistently detected (Lenovo Y700 15ISK)

Does
$ sudo sh -c 'echo -n "elantech" > /sys/bus/serio/devices/serio1/protocol'
still work for you?

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

Title:
  ETPS/2 Elantech Touchpad inconsistently detected (Lenovo Y700 15ISK)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This has been happening reliably on my Lenovo Y700 15ISK since
  15.10... Sometimes it shows up as ETPS/2, sometimes PS/2, sometimes
  Logitech Wheelmouse... Most of the time it shows as "PS/2 Logitech
  Wheel Mouse" but none of the multitouch (2 finger scroll, 3 finger
  middle-click) can be set up. synclient says no device is present.

  This is likely related to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dphillips   1280 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 18 07:40:12 2017
  InstallationDate: Installed on 2017-04-18 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80NV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=8bba488a-b6df-4c29-8a90-8811c1078048 ro quiet splash i8042.kbdreset=1 
vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN53WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN53WW:bd09/19/2016:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
  dmi.product.name: 80NV
  dmi.product.version: Lenovo ideapad Y700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly

Please attach the output of `udevadm info -e`?
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/1743158

Title:
  Trackpad doesn't work proprerly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the 
Elantech trackpad here the two files of the commands:
  1)
  the file was empty because the file doesn't exist

  2)
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1043:1bb0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) 
[8086:1901] (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Skylake PCIe 
Controller (x16) [1043:1bb0]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: fee00238  Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <256ns, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt+ ABWMgmt+
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete+, EqualizationPhase1+
 EqualizationPhase2+, EqualizationPhase3+, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture 
Model [8086:1911]

Re: [Kernel-packages] [Bug 1743125] Wi-Fi doesn't work since 4.4.0-104

> On 17 Jan 2018, at 6:06 PM, alex  wrote:
> 
> Hi,
> 
> yes, I installed proprietary driver via Additional Drivers.
> 
> Should I run `dkms status` running *109 kernel?

Yes, please.

This command shows the same result from all kernel version.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1743125
> 
> Title:
>  Wi-Fi doesn't work since 4.4.0-104
> 
> Status in linux package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  since 4.4.0-104 kernels my Wi-Fi isn't working. It doesn't show up in
>  Network Manager, wireless network device is not visible via
>  ifconfig/ip a l commands, though, it's visible for lspci. I had to
>  revert back to 104 kernel. Wi-Fi card is:
> 
>  Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
>  --- 
>  ApportVersion: 2.20.1-0ubuntu2.15
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  alex   2368 F pulseaudio
>   /dev/snd/controlC1:  alex   2368 F pulseaudio
>  DistroRelease: Ubuntu 16.04
>  EcryptfsInUse: Yes
>  HibernationDevice: RESUME=UUID=1099ad49-ac2e-476a-bf3b-067ac888ee93
>  InstallationDate: Installed on 2014-01-17 (1460 days ago)
>  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
> (20130820.1)
>  IwConfig:
>   tun0  no wireless extensions.
> 
>   lono wireless extensions.
> 
>   eth2  no wireless extensions.
>  MachineType: LENOVO 20238
>  Package: linux (not installed)
>  ProcEnviron:
>   LANGUAGE=en_US
>   TERM=xterm
>   PATH=(custom, no user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
> root=UUID=c6fe4caa-d179-47f7-8762-c31ab4a17c0b ro quiet splash vt.handoff=7
>  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
>  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.4.0-109-generic N/A
>   linux-backports-modules-4.4.0-109-generic  N/A
>   linux-firmware 1.157.14
>  Tags:  xenial
>  Uname: Linux 4.4.0-109-generic x86_64
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  UserGroups:
> 
>  _MarkForUpload: True
>  dmi.bios.date: 12/23/2013
>  dmi.bios.vendor: LENOVO
>  dmi.bios.version: 79CN46WW(V3.05)
>  dmi.board.asset.tag: No Asset Tag
>  dmi.board.name: INVALID
>  dmi.board.vendor: LENOVO
>  dmi.board.version: Not Defined
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: LENOVO
>  dmi.chassis.version: Lenovo G510
>  dmi.modalias: 
> dmi:bvnLENOVO:bvr79CN46WW(V3.05):bd12/23/2013:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510:
>  dmi.product.name: 20238
>  dmi.product.version: Lenovo G510
>  dmi.sys.vendor: LENOVO
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743125/+subscriptions

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

Title:
  Wi-Fi doesn't work since 4.4.0-104

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  since 4.4.0-104 kernels my Wi-Fi isn't working. It doesn't show up in
  Network Manager, wireless network device is not visible via
  ifconfig/ip a l commands, though, it's visible for lspci. I had to
  revert back to 104 kernel. Wi-Fi card is:

  Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2368 F pulseaudio
   /dev/snd/controlC1:  alex   2368 F pulseaudio
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=1099ad49-ac2e-476a-bf3b-067ac888ee93
  InstallationDate: Installed on 2014-01-17 (1460 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  IwConfig:
   tun0  no wireless extensions.
   
   lono wireless extensions.
   
   eth2  no wireless extensions.
  MachineType: LENOVO 20238
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=c6fe4caa-d179-47f7-8762-c31ab4a17c0b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  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:

[Kernel-packages] [Bug 1740971] Re: Can't detect external headset via line-out jack on some Dell machines

2018-01-17 Thread Hui Wang

@Igor,

Is the codec on your machine realtek alc274?

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

Title:
   Can't detect external headset via line-out jack on some Dell machines

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

Bug description:
  insert a headset to line-out jack

  Expected results: system should detect line-out port and sound output
  through line-out jack

  Actual results: Can't detect external headset via line-out jack

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740971/+subscriptions

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

[Kernel-packages] [Bug 1743830] Re: Kernel 4.13.0 update causing x to not load properly using amdgpu graphics on ubuntu 16.04.3

2018-01-17 Thread Xuramaz

I attempted to repeat the issue by installing kernel 4.13.0 using the ukuu 
utility (I couldn't find how to install the exact kernel that created the 
issue, so that I could create a bug report). The exact kernel that ended up 
being installed was 4.13.0-041300-generic. 
On this kernel, I have no issues.

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

Title:
  Kernel 4.13.0 update causing x to not load properly using amdgpu
  graphics on ubuntu 16.04.3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my ubuntu 16.04.3 system, the update to kernal 4.13.0-26.29~16.04.2
  (which also came in installing 4.13.0.26.39,although that wasn't the
  one that was running when the issue occurred).  After a reboot, x
  broke, with the boot initially started on the my left screen (the run
  running on an r9 390), and switched to  my right screen (Running off
  the integrated gpu of my Intel 4690-k), where it looked normal. For
  about two minutes, the screen would very quickly blink about 3 times a
  second. During this period typing was difficult, with many keypresses
  randomly missing. However that issue quickly went away.

  Initially I thought it was a compatibility issue with amdgpu-pro
  (17.04), however once I uninstalled that, the issue continued
  unchanged. (where then my system was running the version of amdgpu
  from the oibaf ppa). Once I managed to return to old kernal, my system
  returned completely back to normal.

  I can tell more system details, however won't help with more details
  of the bug, and I don't want to replicate it and break my system
  again. I am sorry however that I forgot to take a picture of both
  screens to show what was going wrong during boot, and the point at
  where it switched screens.

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

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

[Kernel-packages] [Bug 1743830] Re: Kernel 4.13.0 update causing x to not load properly using amdgpu graphics on ubuntu 16.04.3

2018-01-17 Thread Xuramaz

Sorry, in post #4, when I said "to create a bug report", what I meant
was creating the logs files that the kernel bot asked for in post #2.

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

Title:
  Kernel 4.13.0 update causing x to not load properly using amdgpu
  graphics on ubuntu 16.04.3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my ubuntu 16.04.3 system, the update to kernal 4.13.0-26.29~16.04.2
  (which also came in installing 4.13.0.26.39,although that wasn't the
  one that was running when the issue occurred).  After a reboot, x
  broke, with the boot initially started on the my left screen (the run
  running on an r9 390), and switched to  my right screen (Running off
  the integrated gpu of my Intel 4690-k), where it looked normal. For
  about two minutes, the screen would very quickly blink about 3 times a
  second. During this period typing was difficult, with many keypresses
  randomly missing. However that issue quickly went away.

  Initially I thought it was a compatibility issue with amdgpu-pro
  (17.04), however once I uninstalled that, the issue continued
  unchanged. (where then my system was running the version of amdgpu
  from the oibaf ppa). Once I managed to return to old kernal, my system
  returned completely back to normal.

  I can tell more system details, however won't help with more details
  of the bug, and I don't want to replicate it and break my system
  again. I am sorry however that I forgot to take a picture of both
  screens to show what was going wrong during boot, and the point at
  where it switched screens.

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

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

[Kernel-packages] [Bug 1742764] Re: 4.13.0-26-generic touchpad two finger scroll & tap to click doesn't work after upgrade

2018-01-17 Thread Solaris

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

Title:
   4.13.0-26-generic touchpad two finger scroll & tap to click doesn't
  work after upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  when I use kernel version 4.10.0-42-generic touchpad work as requested
  (two finger scroll & tap to click activated).

  When I use Kernel 4.13.0-26-generic which system ask me to upgrade on,
  two finger scroll & tap to click activated but touchpad doesn't work
  with.

  GOOD:
  4.10.0-42-generic
  xinput
  kam@kam-Flex-3-1580:~$ xinput 
  ⎡ Virtual core pointerid=2[master 
pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  
pointer  (2)]
  ⎜   ↳ AlpsPS/2 ALPS GlidePointid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master 
keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7
[slave  keyboard (3)]
  ↳ Video Bus   id=8
[slave  keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera   id=10   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  kam@kam-Flex-3-1580:~$ 

  
  ===
  BAD:
  4.13.0-26-generic
  xinput

  xxx@xxx-Flex-3-1580:~$ xinput 
  ⎡ Virtual core pointerid=2[master 
pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  
pointer  (2)]
  ⎜   ↳ AlpsPS/2 ALPS GlidePointid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master 
keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7
[slave  keyboard (3)]
  ↳ Video Bus   id=8
[slave  keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera: Lenovo EasyC id=10   [slave  keyboard (3)]
  ↳ Ideapad extra buttons   id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ PEAQ WMI hotkeysid=15   [slave  
keyboard (3)]
  xxx@xxx-Flex-3-1580:~$
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kam2605 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0ab1aa77-c4e5-44b4-8551-2cb8303dd3f2
  InstallationDate: Installed on 2017-06-21 (204 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80R4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic.efi.signed 
root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/10/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN25WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Flex 3-1580
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.ta

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

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel is having problem loading or validating certificates. Looking
  over the internet looks like this is a kernel issue.

  Patchs from other distro:
  https://bugzilla.redhat.com/show_bug.cgi?id=1497559
  - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch
  - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch
  - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch

  
  [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: 
ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734'
  [1.203352] Couldn't get size: 0x800e
  [1.203354] MODSIGN: Couldn't get UEFI db list
  [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate 
Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys 
keyring
  [1.205102] Couldn't get size: 0x800e
  [1.205103] MODSIGN: Couldn't get UEFI dbx list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wellington   1429 F pulseaudio
   /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
   /dev/snd/controlC1:  wellington   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 22:37:13 2018
  HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
  InstallationDate: Installed on 2018-01-16 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD5 R5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-17 Thread André Brait Carneiro Fabotti

@Seth I just confirmed that it does fix the bug.

I forced the re-installation of version 1.157.14 and rebooted. I checked
that the old firmware was loaded and that the files in the
/lib/firmware/ath10k/QCA6174/hw3.0/ folder were indeed the ones that
came with the old package. Then I let the bug happen, which it did.

Then I downloaded your package and installed it with dpkg. Rebooted,
checked that the new firmware was loaded, checked the files and it's
been 5 group rekeyings without any issues.

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Incomplete

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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

[Kernel-packages] [Bug 1743908] [NEW] MODSIGN: Couldn't get UEFI db list

2018-01-17 Thread Wellington Uemura

Public bug reported:

Kernel is having problem loading or validating certificates. Looking
over the internet looks like this is a kernel issue.

Patchs from other distro:
https://bugzilla.redhat.com/show_bug.cgi?id=1497559
- 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch
- 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch
- 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch


[1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: 
ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734'
[1.203352] Couldn't get size: 0x800e
[1.203354] MODSIGN: Couldn't get UEFI db list
[1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate 
Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys 
keyring
[1.205102] Couldn't get size: 0x800e
[1.205103] MODSIGN: Couldn't get UEFI dbx list

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-25-generic 4.13.0-25.29
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  wellington   1429 F pulseaudio
 /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
 /dev/snd/controlC1:  wellington   1429 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 22:37:13 2018
HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
InstallationDate: Installed on 2018-01-16 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
IwConfig:
 lono wireless extensions.
 
 enp7s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-25-generic N/A
 linux-backports-modules-4.13.0-25-generic  N/A
 linux-firmware 1.169.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-UD5 R5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel is having problem loading or validating certificates. Looking
  over the internet looks like this is a kernel issue.

  Patchs from other distro:
  https://bugzilla.redhat.com/show_bug.cgi?id=1497559
  - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch
  - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch
  - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch

  
  [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: 
ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734'
  [1.203352] Couldn't get size: 0x800e
  [1.203354] MODSIGN: Couldn't get UEFI db list
  [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate 
Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys 
keyring
  [1.205102] Couldn't get size: 0x800e
  [1.205103] MODSIGN: Couldn't get UEFI dbx list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wellington   1429 F pulseaudio
   /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
   /dev/snd/controlC1:  wellington   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 22:37:13 2018
  HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
  InstallationDate: Ins

[Kernel-packages] [Bug 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

2018-01-17 Thread Tim Starling

edc2988c548db05e33b921fed15821010bc74895: fixed

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

Title:
  Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

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

Bug description:
  I'm following the HWE kernels in Ubuntu 16.04, so my kernel was
  upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the
  splash screen and disk encryption passphrase prompt showed correctly,
  but when X started, the screen went blank. Logs showed everything
  running as normal despite the blank screen. Rebooting with the
  "nomodeset" kernel parameter fixed the issue but is not suitable as a
  permanent workaround since it disables my external monitor. Rebooting
  back into 4.10 also fixed the issue.

  I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried
  both intel and fbdev X drivers, both gave a blank screen.

  lsb_release: Ubuntu 16.04.3 LTS

  dpkg-query -W:

  linux-signed-image-generic-hwe-16.04  4.13.0.26.46
  xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1
  xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1
  xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1

  In Xorg.0.log with fbdev, I saw:

  [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument

  repeated 239 times.

  Typical kernel messages attached (from kern.log, reformatted to look
  like dmesg).

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

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

[Kernel-packages] [Bug 1733662] Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/17/2018 05:55 PM, Thomas Gleixner wrote:
> On Wed, 17 Jan 2018, Joseph Salisbury wrote:
>> On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
>>
>> Testing of your patch shows that your patch resolves the bug.  Thanks
>> for the assistance!  Is this something you could submit to mainline?
> Already there :)
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d47924417319e3b6a728c0b690f183e75bc2a702
>
> Tagged for stable.
>
> Thanks,
>
>   tglx

Thanks so much!

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1733662] Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

2018-01-17 Thread tglx

On Wed, 17 Jan 2018, Joseph Salisbury wrote:
> On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
> 
> Testing of your patch shows that your patch resolves the bug.  Thanks
> for the assistance!  Is this something you could submit to mainline?

Already there :)

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d47924417319e3b6a728c0b690f183e75bc2a702

Tagged for stable.

Thanks,

tglx

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1743041] Re: Updating Lubuntu on netbook corrupts screen

2018-01-17 Thread Mike Lewis

OK, I'll do that.

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

Title:
  Updating Lubuntu on netbook corrupts screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updating Lubuntu 16.04-3 LTS on Asus 1000HE netbook corrupts screen as
  shown at https://i.imgur.com/bTw9t4Z.jpg

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

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

[Kernel-packages] [Bug 1733662] Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
> On Tue, 16 Jan 2018, Yu, Fenghua wrote:
>>> From: Thomas Gleixner [mailto:t...@linutronix.de]
>> Is this a Haswell specific issue?
>>
>> I run the following test forever without issue on Broadwell and 4.15.0-rc6 
>> with rdt mounted:
>> for ((;;)) do
>> for ((i=1;i<88;i++)) do
>> echo 0 >/sys/devices/system/cpu/cpu$i/online
>> done
>> echo "online cpus:"
>> grep processor /proc/cpuinfo |wc
>> for ((i=1;i<88;i++)) do
>> echo 1 >/sys/devices/system/cpu/cpu$i/online
>> done
>> echo "online cpus:"
>> grep processor /proc/cpuinfo|wc
>> done
>>
>> I'm finding a Haswell to reproduce the issue.
> Come on. This is crystal clear from the KASAN trace. And the fix is simple 
> enough.
>
> You simply do not run into it because on your machine
>
> is_llc_occupancy_enabled() is false...
>
> Thanks,
>
>   tglx
>   
> 8<
>
> diff --git a/arch/x86/kernel/cpu/intel_rdt.c b/arch/x86/kernel/cpu/intel_rdt.c
> index 88dcf8479013..99442370de40 100644
> --- a/arch/x86/kernel/cpu/intel_rdt.c
> +++ b/arch/x86/kernel/cpu/intel_rdt.c
> @@ -525,10 +525,6 @@ static void domain_remove_cpu(int cpu, struct 
> rdt_resource *r)
>*/
>   if (static_branch_unlikely(&rdt_mon_enable_key))
>   rmdir_mondata_subdir_allrdtgrp(r, d->id);
> - kfree(d->ctrl_val);
> - kfree(d->rmid_busy_llc);
> - kfree(d->mbm_total);
> - kfree(d->mbm_local);
>   list_del(&d->list);
>   if (is_mbm_enabled())
>   cancel_delayed_work(&d->mbm_over);
> @@ -545,6 +541,10 @@ static void domain_remove_cpu(int cpu, struct 
> rdt_resource *r)
>   cancel_delayed_work(&d->cqm_limbo);
>   }
>  
> + kfree(d->ctrl_val);
> + kfree(d->rmid_busy_llc);
> + kfree(d->mbm_total);
> + kfree(d->mbm_local);
>   kfree(d);
>   return;
>   }

Hi Thomas,

Testing of your patch shows that your patch resolves the bug.  Thanks
for the assistance!  Is this something you could submit to mainline?

Thanks,


Joe

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1743766] Re: reboot/IKVM problems on Ubuntu 14.04

Can you see if the 3.13.0-136 kernel has this bug as well?  It is pre
pti patches and can be downloaded from:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/13786576

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

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

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

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

** Tags added: kernel-da-key pti

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

Title:
  reboot/IKVM problems on Ubuntu 14.04

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete

Bug description:
  On the 3.13.0-52-generic #86-Ubuntu kernel server worked perfectly fine.
  To mitigate meltdown vulnerability updated kernel to 3.13.0-139-generic 
#188-Ubuntu.

  Approximately one hour after system boots I get this bug. I can`t access 
server via IKVM(ssh works fine).
  Also I got problem with server reboot. On "reboot" or "init 6" commands 
server halts. Only option is to reset server via IPMI. After server reseted and 
system boots, IKVM and reboot works as intended for approximately one hour. 
Then bug is repeated.

  linux-image-3.13.0-139-generic:
Installed: 3.13.0-139.188
Candidate: 3.13.0-139.188

  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

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

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

[Kernel-packages] [Bug 1743812] Re: CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

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

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

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

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

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

** Tags added: pti

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

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

Bug description:
  Hello,

  I'm testing script:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/



  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [sudo] password for caravena: 
  Spectre and Meltdown mitigation detection tool v0.31

  Checking for vulnerabilities against running kernel Linux 4.13.0-30-generic 
#33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64
  CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz

  CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
  * Checking count of LFENCE opcodes in kernel:  YES 
  > STATUS:  NOT VULNERABLE  (114 opcodes found, which is >= 70, heuristic to 
be improved when official patches become available)

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
  *   Hardware (CPU microcode) support for mitigation
  * The SPEC_CTRL MSR is available:  NO 
  * The SPEC_CTRL CPUID feature bit is set:  NO 
  *   Kernel support for IBRS:  YES 
  *   IBRS enabled for Kernel space:  NO 
  *   IBRS enabled for User space:  NO 
  * Mitigation 2
  *   Kernel compiled with retpoline option:  NO 
  *   Kernel compiled with a retpoline-aware compiler:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
  * Kernel supports Page Table Isolation (PTI):  YES 
  * PTI enabled and active:  YES 
  * Checking if we're running under Xen PV (64 bits):  NO 
  > STATUS:  NOT VULNERABLE  (PTI mitigates the vulnerability)

  A false sense of security is worse than no security at all, see
  --disclaimer

  
  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1743859] Re: SCSI subsystem Kernel

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

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

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

** Tags added: needs-bisect

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

Title:
  SCSI subsystem Kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Version Signature
  Ubuntu 4.4.0-109.132-generic 4.4.98

  Attached is source code for sending a scsi command block to a sg
  device. When this is executed it causes a a seg fault with the stack
  dump that can been seen in the dmesg logs(see Below). The code worked
  until 4.4.0-98. It also continues to work on newer versions of ubuntu,
  such as Ubuntu 17.10 with the most up to date kernel 4.13.0.25.
  Please let me know if there is anything else information wise I can do
  help clarify this error. I have been able to replicate this on
  multiple hardware scenarios so I hope that the attached source code
  should be enough for you to do the same.

  [  107.963701] Call Trace:
  [  107.963715]  [] dump_stack+0x63/0x90
  [  107.963727]  [] warn_slowpath_common+0x82/0xc0
  [  107.963729]  [] warn_slowpath_null+0x1a/0x20
  [  107.963731]  [] sg_rq_end_io+0x24e/0x340
  [  107.963741]  [] ? add_timer_randomness+0xde/0x100
  [  107.963745]  [] blk_finish_request+0x62/0xf0
  [  107.963748]  [] scsi_end_request+0x106/0x1d0
  [  107.963750]  [] scsi_io_completion+0x1b6/0x690
  [  107.963752]  [] scsi_finish_command+0xcf/0x120
  [  107.963754]  [] scsi_eh_flush_done_q+0xf5/0x140
  [  107.963760]  [] ata_scsi_port_error_handler+0x599/0x770
  [  107.963763]  [] ? ata_scsi_cmd_error_handler+0x11d/0x150
  [  107.963765]  [] ata_scsi_error+0xa0/0xe0
  [  107.963766]  [] scsi_error_handler+0xdb/0x8a0
  [  107.963779]  [] ? __schedule+0x310/0x7b0
  [  107.963781]  [] ? scsi_eh_get_sense+0x240/0x240
  [  107.963788]  [] kthread+0xe5/0x100
  [  107.963790]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  107.963792]  [] ret_from_fork+0x3f/0x70
  [  107.963794]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  107.963795] ---[ end trace b723db66c786bceb ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-109-generic 4.4.0-109.132
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jan 17 12:34:22 2018
  HibernationDevice: RESUME=/dev/mapper/pc17--vg-swap_1
  InstallationDate: Installed on 2018-01-17 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   lono wireless extensions.
   
   ens192no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic 
root=/dev/mapper/hostname--vg-root ro
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/14/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.pro

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe

That seems to have fixed it! I've run the test script six or seven times
on both kernels, with nary a hiccup (aside from the "error -19" messages
with the 4.13 kernel). Below is the reported kernel information from
both your builds, just to be sure I booted the correct kernels.

$ uname -a
Linux oil-boldore 4.13.0-25-generic #29~lp1733662PatchFromUpstream SMP Wed Jan 
17 20:13:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ uname -a
Linux oil-boldore 4.15.0-041500rc8-generic #201801172011 SMP Wed Jan 17 
20:13:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1743830] Re: Kernel 4.13.0 update causing x to not load properly using amdgpu graphics on ubuntu 16.04.3

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

Thank you in advance!

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

** Tags added: kernel-da-key

** Tags added: needs-bisect

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

Title:
  Kernel 4.13.0 update causing x to not load properly using amdgpu
  graphics on ubuntu 16.04.3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my ubuntu 16.04.3 system, the update to kernal 4.13.0-26.29~16.04.2
  (which also came in installing 4.13.0.26.39,although that wasn't the
  one that was running when the issue occurred).  After a reboot, x
  broke, with the boot initially started on the my left screen (the run
  running on an r9 390), and switched to  my right screen (Running off
  the integrated gpu of my Intel 4690-k), where it looked normal. For
  about two minutes, the screen would very quickly blink about 3 times a
  second. During this period typing was difficult, with many keypresses
  randomly missing. However that issue quickly went away.

  Initially I thought it was a compatibility issue with amdgpu-pro
  (17.04), however once I uninstalled that, the issue continued
  unchanged. (where then my system was running the version of amdgpu
  from the oibaf ppa). Once I managed to return to old kernal, my system
  returned completely back to normal.

  I can tell more system details, however won't help with more details
  of the bug, and I don't want to replicate it and break my system
  again. I am sorry however that I forgot to take a picture of both
  screens to show what was going wrong during boot, and the point at
  where it switched screens.

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

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

[Kernel-packages] [Bug 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

I built the next test kernel, up to the following commit:
edc2988c548db05e33b921fed15821010bc74895

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1742602

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

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

Bug description:
  I'm following the HWE kernels in Ubuntu 16.04, so my kernel was
  upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the
  splash screen and disk encryption passphrase prompt showed correctly,
  but when X started, the screen went blank. Logs showed everything
  running as normal despite the blank screen. Rebooting with the
  "nomodeset" kernel parameter fixed the issue but is not suitable as a
  permanent workaround since it disables my external monitor. Rebooting
  back into 4.10 also fixed the issue.

  I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried
  both intel and fbdev X drivers, both gave a blank screen.

  lsb_release: Ubuntu 16.04.3 LTS

  dpkg-query -W:

  linux-signed-image-generic-hwe-16.04  4.13.0.26.46
  xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1
  xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1
  xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1

  In Xorg.0.log with fbdev, I saw:

  [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument

  repeated 239 times.

  Typical kernel messages attached (from kern.log, reformatted to look
  like dmesg).

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

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

[Kernel-packages] [Bug 1743872] Re: Not work 802.11ac WLAN Adapter

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc8

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

Title:
  Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1743830] Missing required logs.

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 1743830

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

Title:
  Kernel 4.13.0 update causing x to not load properly using amdgpu
  graphics on ubuntu 16.04.3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my ubuntu 16.04.3 system, the update to kernal 4.13.0-26.29~16.04.2
  (which also came in installing 4.13.0.26.39,although that wasn't the
  one that was running when the issue occurred).  After a reboot, x
  broke, with the boot initially started on the my left screen (the run
  running on an r9 390), and switched to  my right screen (Running off
  the integrated gpu of my Intel 4690-k), where it looked normal. For
  about two minutes, the screen would very quickly blink about 3 times a
  second. During this period typing was difficult, with many keypresses
  randomly missing. However that issue quickly went away.

  Initially I thought it was a compatibility issue with amdgpu-pro
  (17.04), however once I uninstalled that, the issue continued
  unchanged. (where then my system was running the version of amdgpu
  from the oibaf ppa). Once I managed to return to old kernal, my system
  returned completely back to normal.

  I can tell more system details, however won't help with more details
  of the bug, and I don't want to replicate it and break my system
  again. I am sorry however that I forgot to take a picture of both
  screens to show what was going wrong during boot, and the point at
  where it switched screens.

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

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

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-01-17 Thread jessepage1989

Same thing happened to me. When I tried to reboot with previous kernel the 
mouse and keyboard would disappear. Removing Nvidia driver got me back to the 
desktop. 
In my case original nvidia drivers was the cause and switching back to open 
source nouveau helped. First, I removed all stuff from nvidia:

1. sudo apt-get remove --purge 'nvidia-*'
2. sudo apt-get install ubuntu-desktop
3. sudo rm /etc/X11/xorg.conf
4. echo 'nouveau' | sudo tee -a /etc/modules
(source: How can I uninstall a nvidia driver completely ?)

After that I could login, but unity didn't load, there was no launcher
etc. It turn out I had to re-enable Unity plugin:

5. sudo apt-get install compizconfig-settings-manager
6. DISPLAY=:0 ccsm
7. Find the Unity plugin and enable it.
(source: Unity doesn't load, no Launcher, no Dash appears)

Found this solution in one of the Ubuntu forums. Steps 6 and 7 didn't
apply to me so I just rebooted after and I could log in.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1743204] Re: Segmentation fault in "apt --fix-broken install"

2018-01-17 Thread Otto

There is one file in /usr/lib/x86_64-linux-gnu/wine/ which lsattr says
has the immutable flag set:

---I--e /usr/lib/x86_64-linux-gnu/wine/fakedlls

Is this the root of the problem?

The file "/usr/lib/x86_64-linux-gnu/wine/resutils.dll.so.dpkg-new" (see
above) does not (currently) exist, so the permissions problem must be
created in the update process.

Or am I barking up the wrong tree? What does the package maintainer say?

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

Title:
  Segmentation fault in "apt --fix-broken install"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected: New installation of 'wine'

  Result: (See attached screenshot of the terminal.)
  The installation failed with unmet dependencies, so I entered "sudo apt 
--fix-broken install" and in the course of this dpkg encountered a segmentation 
fault:

  Unpacking linux-image-extra-4.13.0-25-generic (4.13.0-25.29) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb
 (--unpack):
   unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.13.0-25-generic.list-new': Operation 
not permitted
  Segmentation fault

  I have seen this before reported as a bug: 1742387

  As I cannot attach more than one file (why this?) I'm inserting the
  full terminal content here:

  sudo apt install wine-stable
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies.
   linux-image-generic : Depends: linux-image-extra-4.13.0-25-generic but it is 
not going to be installed
   wine-stable : Depends: wine64 (>= 2.0.2-2ubuntu1) but it is not going to be 
installed or
  wine32 (>= 2.0.2-2ubuntu1)
 Depends: wine64 (< 2.0.2-2ubuntu1.1~) but it is not going to 
be installed or
  wine32 (< 2.0.2-2ubuntu1.1~)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  11:20:56 [root@scotland] ~
  sudo apt --fix-broken install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
linux-image-extra-4.13.0-25-generic
  The following NEW packages will be installed
linux-image-extra-4.13.0-25-generic
  0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
  6 not fully installed or removed.
  Need to get 0 B/31.5 MB of archives.
  After this operation, 163 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 383838 files and directories currently installed.)
  Preparing to unpack 
.../linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb ...
  Unpacking linux-image-extra-4.13.0-25-generic (4.13.0-25.29) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb
 (--unpack):
   unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.13.0-25-generic.list-new': Operation 
not permitted
  Segmentation fault

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.13.0.25.26
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  john   6019 F pulseaudio
   /dev/snd/controlC1:  john   6019 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jan 14 11:24:06 2018
  HibernationDevice: RESUME=UUID=53ca4e3e-a7f4-4969-ad38-429b38324fed
  InstallationDate: Installed on 2017-04-28 (260 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=4cfb4fad-eedb-4de1-9dd6-b384d7bc18e0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-08 (66 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-DS4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd09/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS4:pvr:

[Kernel-packages] [Bug 1743830] Re: Kernel 4.13.0 update causing x to not load properly using amdgpu graphics on ubuntu 16.04.3

2018-01-17 Thread Brian Murray

** Tags added: regression-update

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

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

Title:
  Kernel 4.13.0 update causing x to not load properly using amdgpu
  graphics on ubuntu 16.04.3

Status in linux package in Ubuntu:
  New

Bug description:
  On my ubuntu 16.04.3 system, the update to kernal 4.13.0-26.29~16.04.2
  (which also came in installing 4.13.0.26.39,although that wasn't the
  one that was running when the issue occurred).  After a reboot, x
  broke, with the boot initially started on the my left screen (the run
  running on an r9 390), and switched to  my right screen (Running off
  the integrated gpu of my Intel 4690-k), where it looked normal. For
  about two minutes, the screen would very quickly blink about 3 times a
  second. During this period typing was difficult, with many keypresses
  randomly missing. However that issue quickly went away.

  Initially I thought it was a compatibility issue with amdgpu-pro
  (17.04), however once I uninstalled that, the issue continued
  unchanged. (where then my system was running the version of amdgpu
  from the oibaf ppa). Once I managed to return to old kernal, my system
  returned completely back to normal.

  I can tell more system details, however won't help with more details
  of the bug, and I don't want to replicate it and break my system
  again. I am sorry however that I forgot to take a picture of both
  screens to show what was going wrong during boot, and the point at
  where it switched screens.

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

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

[Kernel-packages] [Bug 1743830] [NEW] Kernel 4.13.0 update causing x to not load properly using amdgpu graphics on ubuntu 16.04.3

2018-01-17 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

On my ubuntu 16.04.3 system, the update to kernal 4.13.0-26.29~16.04.2
(which also came in installing 4.13.0.26.39,although that wasn't the one
that was running when the issue occurred).  After a reboot, x broke,
with the boot initially started on the my left screen (the run running
on an r9 390), and switched to  my right screen (Running off the
integrated gpu of my Intel 4690-k), where it looked normal. For about
two minutes, the screen would very quickly blink about 3 times a second.
During this period typing was difficult, with many keypresses randomly
missing. However that issue quickly went away.

Initially I thought it was a compatibility issue with amdgpu-pro
(17.04), however once I uninstalled that, the issue continued unchanged.
(where then my system was running the version of amdgpu from the oibaf
ppa). Once I managed to return to old kernal, my system returned
completely back to normal.

I can tell more system details, however won't help with more details of
the bug, and I don't want to replicate it and break my system again. I
am sorry however that I forgot to take a picture of both screens to show
what was going wrong during boot, and the point at where it switched
screens.

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


** Tags: bot-comment regression-update
-- 
Kernel 4.13.0 update causing x to not load properly using amdgpu graphics on 
ubuntu 16.04.3
https://bugs.launchpad.net/bugs/1743830
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 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe

I built Artful and mainline test kernels with the patch from tglx.  The
test kernels can be downloaded from:

Artful: http://kernel.ubuntu.com/~jsalisbury/lp1733662/artful
mainline: http://kernel.ubuntu.com/~jsalisbury/lp1733662/mainline

Can you test these kernels out and see if they resolve the bug?

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

2018-01-17 Thread Tim Starling

bf1d6b2c76eda86159519bf5c427b1fa8f51f733: fixed

Curiously, there was a kernel error with this kernel which I don't think
was there before:

[5.505217] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* 
uncleared fifo underrun on pipe A
[5.505308] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun

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

Title:
  Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

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

Bug description:
  I'm following the HWE kernels in Ubuntu 16.04, so my kernel was
  upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the
  splash screen and disk encryption passphrase prompt showed correctly,
  but when X started, the screen went blank. Logs showed everything
  running as normal despite the blank screen. Rebooting with the
  "nomodeset" kernel parameter fixed the issue but is not suitable as a
  permanent workaround since it disables my external monitor. Rebooting
  back into 4.10 also fixed the issue.

  I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried
  both intel and fbdev X drivers, both gave a blank screen.

  lsb_release: Ubuntu 16.04.3 LTS

  dpkg-query -W:

  linux-signed-image-generic-hwe-16.04  4.13.0.26.46
  xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1
  xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1
  xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1

  In Xorg.0.log with fbdev, I saw:

  [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument

  repeated 239 times.

  Typical kernel messages attached (from kern.log, reformatted to look
  like dmesg).

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

2018-01-17 Thread Dimitri John Ledkov

yes, but I'm not uploading systemd until after the build-farm is open.

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

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

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

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

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

  ### To run the test ###

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1743872] Re: Not work Dual Band USB Adapter 8811AU11MAY

2018-01-17 Thread Cristian Aravena Romero

Hello,

dmesg_4.15.0-041500rc8-generic

dmesg:
[  104.468231] usb 3-2: new high-speed USB device number 4 using xhci_hcd
[  104.616570] usb 3-2: New USB device found, idVendor=0bda, idProduct=a811
[  104.616578] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  104.616582] usb 3-2: Product: 802.11ac WLAN Adapter 
[  104.616585] usb 3-2: Manufacturer: Realtek 
[  104.616588] usb 3-2: SerialNumber: 00e04c01

Regards,
--
Cristian

** Attachment added: "dmesg_4.15.0-041500rc8-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743872/+attachment/5038469/+files/dmesg_4.15.0-041500rc8-generic.txt

** Summary changed:

- Not work Dual Band USB Adapter 8811AU11MAY
+ Not work 802.11ac WLAN Adapter

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

Title:
  Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash

2018-01-17 Thread Christian List

#5
Using the test kernel I can confirm, that the BIOS is writable, keeps settings 
over reboot and the bios changed message has disappeared.
Thanks a lot!

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

Title:
  Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix
  of Intel SPI bug on certain serial flash

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

Bug description:
  New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI
  bug in kernel Edit"

  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.

  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:

  intel-spi intel-spi: s25fl064k (8192 Kbytes)

  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10

  
  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."

  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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

[Kernel-packages] [Bug 1733662] Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
> On Tue, 16 Jan 2018, Yu, Fenghua wrote:
>>> From: Thomas Gleixner [mailto:t...@linutronix.de]
>> Is this a Haswell specific issue?
>>
>> I run the following test forever without issue on Broadwell and 4.15.0-rc6 
>> with rdt mounted:
>> for ((;;)) do
>> for ((i=1;i<88;i++)) do
>> echo 0 >/sys/devices/system/cpu/cpu$i/online
>> done
>> echo "online cpus:"
>> grep processor /proc/cpuinfo |wc
>> for ((i=1;i<88;i++)) do
>> echo 1 >/sys/devices/system/cpu/cpu$i/online
>> done
>> echo "online cpus:"
>> grep processor /proc/cpuinfo|wc
>> done
>>
>> I'm finding a Haswell to reproduce the issue.
> Come on. This is crystal clear from the KASAN trace. And the fix is simple 
> enough.
>
> You simply do not run into it because on your machine
>
> is_llc_occupancy_enabled() is false...
>
> Thanks,
>
>   tglx
>   
> 8<
>
> diff --git a/arch/x86/kernel/cpu/intel_rdt.c b/arch/x86/kernel/cpu/intel_rdt.c
> index 88dcf8479013..99442370de40 100644
> --- a/arch/x86/kernel/cpu/intel_rdt.c
> +++ b/arch/x86/kernel/cpu/intel_rdt.c
> @@ -525,10 +525,6 @@ static void domain_remove_cpu(int cpu, struct 
> rdt_resource *r)
>*/
>   if (static_branch_unlikely(&rdt_mon_enable_key))
>   rmdir_mondata_subdir_allrdtgrp(r, d->id);
> - kfree(d->ctrl_val);
> - kfree(d->rmid_busy_llc);
> - kfree(d->mbm_total);
> - kfree(d->mbm_local);
>   list_del(&d->list);
>   if (is_mbm_enabled())
>   cancel_delayed_work(&d->mbm_over);
> @@ -545,6 +541,10 @@ static void domain_remove_cpu(int cpu, struct 
> rdt_resource *r)
>   cancel_delayed_work(&d->cqm_limbo);
>   }
>  
> + kfree(d->ctrl_val);
> + kfree(d->rmid_busy_llc);
> + kfree(d->mbm_total);
> + kfree(d->mbm_local);
>   kfree(d);
>   return;
>   }

Thanks, Thomas.  I'll build some test kernels and have your patch tested
out.


Thanks,


Joe

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1743872] [NEW] Not work Dual Band USB Adapter 8811AU11MAY

2018-01-17 Thread Cristian Aravena Romero

Public bug reported:

Hello,

Not work:
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

Regards,
--
Cristian

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

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


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

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

Title:
  Not work Dual Band USB Adapter 8811AU11MAY

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

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

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

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

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

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

Title:
  Not work Dual Band USB Adapter 8811AU11MAY

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1743204] Re: Segmentation fault in "apt --fix-broken install"

2018-01-17 Thread Otto

I tried to install wine again and got more errors - see the attached
terminal log. The base problem seems always to be a authorisation issue.
e.g.:

"dpkg: error processing archive 
/var/cache/apt/archives/libwine_2.0.2-2ubuntu1_amd64.deb (--unpack):
 unable to open '/usr/lib/x86_64-linux-gnu/wine/resutils.dll.so.dpkg-new': 
Operation not permitted"

Can someone with more know-how than myself divine what the underlying
problem is?

>From my naive googling it seems to be a problem with "immutable flag set
in its extended attributes" as in
"https://askubuntu.com/questions/675296/changing-ownership-operation-
not-permitted-even-as-root"

The permissions of " /usr/lib/x86_64-linux-gnu/wine" seem to me to be in order 
e.g.:
-rw-r--r--   1 root root   79K Oct 13 12:09 acledit.dll.so

How can we proceed in this matter?


** Attachment added: "Terminal log of the error"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743204/+attachment/5038450/+files/ubuntu-bug-3.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/1743204

Title:
  Segmentation fault in "apt --fix-broken install"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected: New installation of 'wine'

  Result: (See attached screenshot of the terminal.)
  The installation failed with unmet dependencies, so I entered "sudo apt 
--fix-broken install" and in the course of this dpkg encountered a segmentation 
fault:

  Unpacking linux-image-extra-4.13.0-25-generic (4.13.0-25.29) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb
 (--unpack):
   unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.13.0-25-generic.list-new': Operation 
not permitted
  Segmentation fault

  I have seen this before reported as a bug: 1742387

  As I cannot attach more than one file (why this?) I'm inserting the
  full terminal content here:

  sudo apt install wine-stable
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies.
   linux-image-generic : Depends: linux-image-extra-4.13.0-25-generic but it is 
not going to be installed
   wine-stable : Depends: wine64 (>= 2.0.2-2ubuntu1) but it is not going to be 
installed or
  wine32 (>= 2.0.2-2ubuntu1)
 Depends: wine64 (< 2.0.2-2ubuntu1.1~) but it is not going to 
be installed or
  wine32 (< 2.0.2-2ubuntu1.1~)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  11:20:56 [root@scotland] ~
  sudo apt --fix-broken install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
linux-image-extra-4.13.0-25-generic
  The following NEW packages will be installed
linux-image-extra-4.13.0-25-generic
  0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
  6 not fully installed or removed.
  Need to get 0 B/31.5 MB of archives.
  After this operation, 163 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 383838 files and directories currently installed.)
  Preparing to unpack 
.../linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb ...
  Unpacking linux-image-extra-4.13.0-25-generic (4.13.0-25.29) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb
 (--unpack):
   unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.13.0-25-generic.list-new': Operation 
not permitted
  Segmentation fault

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.13.0.25.26
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  john   6019 F pulseaudio
   /dev/snd/controlC1:  john   6019 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jan 14 11:24:06 2018
  HibernationDevice: RESUME=UUID=53ca4e3e-a7f4-4969-ad38-429b38324fed
  InstallationDate: Installed on 2017-04-28 (260 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=4cfb4fad-eedb-4de1-9dd6-b384d7bc18e0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKi

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

2018-01-17 Thread Eduardo Rudas

Excellent! Hope the commits are included soon in the coming updates.
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/1743269

Title:
  P-state not working in kernel 4.13

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

Bug description:
  I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm
  using Xubuntu 17.10 (Description:Ubuntu 17.10, Release:  17.10). I
  use tlp 1.0-1~artful in order to improve battery performance,
  particularly enabling the Intel P-state performance scaling. In
  Xubuntu 17.04 it worked flawlessly, but when I upgraded to 17.10 the
  processor doesn't scale anymore. I ran all the updates and it's not
  working. I also did a clean install using another hard drive and the
  problem persist.

  I searched the tlp forums and similar problems pointed to a kernel
  bug, so I'm filing this report.

  I tested different mainline kernels in order to see what kernel
  version is causing the problem:

  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels

I was unable to reproduce this problem on the Dell T110; however, I did
notice that it failed the test at the point where the T710 rebooted.
("Stress test for UEFI miscellaneous runtime service")

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

Title:
  "fwts uefirtmisc" causes reboot in recent kernels

Status in Provider for Plainbox - Checkbox:
  Invalid
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels

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

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

Title:
  "fwts uefirtmisc" causes reboot in recent kernels

Status in Provider for Plainbox - Checkbox:
  Invalid
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

Thanks again for testing.  I'll submit an SRU request to have these two
commits included in the Ubuntu 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/1743269

Title:
  P-state not working in kernel 4.13

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

Bug description:
  I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm
  using Xubuntu 17.10 (Description:Ubuntu 17.10, Release:  17.10). I
  use tlp 1.0-1~artful in order to improve battery performance,
  particularly enabling the Intel P-state performance scaling. In
  Xubuntu 17.04 it worked flawlessly, but when I upgraded to 17.10 the
  processor doesn't scale anymore. I ran all the updates and it's not
  working. I also did a clean install using another hard drive and the
  problem persist.

  I searched the tlp forums and similar problems pointed to a kernel
  bug, so I'm filing this report.

  I tested different mainline kernels in order to see what kernel
  version is causing the problem:

  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels

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

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

Title:
  "fwts uefirtmisc" causes reboot in recent kernels

Status in Provider for Plainbox - Checkbox:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels

I tried running apport-collect, as requested by the Ubuntu Kernel Bot,
but it didn't work; it tried to open a (text-based) browser, but that
hung on "Opening socket", presumably because the system in question
is behind strict firewalls in 1SS.

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1743799

Title:
  "fwts uefirtmisc" causes reboot in recent kernels

Status in Provider for Plainbox - Checkbox:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

[Kernel-packages] [Bug 1743799] Re: miscellanea/fwts_test causes reboot

I've managed to isolate this to the fwts "uefirtmisc" test:

$ sudo fwts uefirtmisc
Running 1 tests, results appended to results.log
Test: UEFI miscellaneous runtime service interface tests.   
  Test for UEFI miscellaneous runtime service interfaces. 1 passed, 5 skipped  
Timeout, server 10.1.11.176 not responding.e service interfaces. :  33.3% |

(That last line is partially overwritten by the SSH termination
message.) At 33.3% through that test, the system spontaneously reboots.
None of the other fwts tests causes any problem.

Oddly, the problem disappeared briefly during my testing. This occurred
just after I removed the 4.4.0-109 kernel, and a run of fwts produced a
message about it being unable to run some tests because it couldn't
parse EFI data, but that a reboot should fix the problem. (Sorry, I
didn't save the exact wording of the message.) I suspect this was
related to EFI variable storage and garbage collection. When I rebooted,
the problem reappeared.

Some further notes:

* The system is rather old (we got it in 2009).
* The system is running the latest firmware, version 6.4.0, released in 2013.
* The UEFI version is rather old (2.1.0).
* It's booted in UEFI mode (of course).

I'm going to try re-creating this problem with a Dell T110 of similar
vintage. For the moment, I'll leave lucuma, the system with the problem,
in its current Ubuntu 14.04 configuration. I can run further tests as
directed. As this looks like a kernel bug, or possibly a bug in fwts,
I'll mark this as "invalid" for plainbox-provider-checkbox.

** Changed in: plainbox-provider-checkbox
   Status: New => Invalid

** Summary changed:

- miscellanea/fwts_test causes reboot
+ "fwts uefirtmisc" causes reboot in recent kernels

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

Title:
  "fwts uefirtmisc" causes reboot in recent kernels

Status in Provider for Plainbox - Checkbox:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

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

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

Title:
  SCSI subsystem Kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Version Signature
  Ubuntu 4.4.0-109.132-generic 4.4.98

  Attached is source code for sending a scsi command block to a sg
  device. When this is executed it causes a a seg fault with the stack
  dump that can been seen in the dmesg logs(see Below). The code worked
  until 4.4.0-98. It also continues to work on newer versions of ubuntu,
  such as Ubuntu 17.10 with the most up to date kernel 4.13.0.25.
  Please let me know if there is anything else information wise I can do
  help clarify this error. I have been able to replicate this on
  multiple hardware scenarios so I hope that the attached source code
  should be enough for you to do the same.

  [  107.963701] Call Trace:
  [  107.963715]  [] dump_stack+0x63/0x90
  [  107.963727]  [] warn_slowpath_common+0x82/0xc0
  [  107.963729]  [] warn_slowpath_null+0x1a/0x20
  [  107.963731]  [] sg_rq_end_io+0x24e/0x340
  [  107.963741]  [] ? add_timer_randomness+0xde/0x100
  [  107.963745]  [] blk_finish_request+0x62/0xf0
  [  107.963748]  [] scsi_end_request+0x106/0x1d0
  [  107.963750]  [] scsi_io_completion+0x1b6/0x690
  [  107.963752]  [] scsi_finish_command+0xcf/0x120
  [  107.963754]  [] scsi_eh_flush_done_q+0xf5/0x140
  [  107.963760]  [] ata_scsi_port_error_handler+0x599/0x770
  [  107.963763]  [] ? ata_scsi_cmd_error_handler+0x11d/0x150
  [  107.963765]  [] ata_scsi_error+0xa0/0xe0
  [  107.963766]  [] scsi_error_handler+0xdb/0x8a0
  [  107.963779]  [] ? __schedule+0x310/0x7b0
  [  107.963781]  [] ? scsi_eh_get_sense+0x240/0x240
  [  107.963788]  [] kthread+0xe5/0x100
  [  107.963790]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  107.963792]  [] ret_from_fork+0x3f/0x70
  [  107.963794]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  107.963795] ---[ end trace b723db66c786bceb ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-109-generic 4.4.0-109.132
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jan 17 12:34:22 2018
  HibernationDevice: RESUME=/dev/mapper/pc17--vg-swap_1
  InstallationDate: Installed on 2018-01-17 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   lono wireless extensions.
   
   ens192no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic 
root=/dev/mapper/hostname--vg-root ro
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/14/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1743859] [NEW] SCSI subsystem Kernel

2018-01-17 Thread ======

Public bug reported:

Version Signature
Ubuntu 4.4.0-109.132-generic 4.4.98

Attached is source code for sending a scsi command block to a sg device.
When this is executed it causes a a seg fault with the stack dump that
can been seen in the dmesg logs(see Below). The code worked until
4.4.0-98. It also continues to work on newer versions of ubuntu, such as
Ubuntu 17.10 with the most up to date kernel 4.13.0.25.  Please let me
know if there is anything else information wise I can do help clarify
this error. I have been able to replicate this on multiple hardware
scenarios so I hope that the attached source code should be enough for
you to do the same.

[  107.963701] Call Trace:
[  107.963715]  [] dump_stack+0x63/0x90
[  107.963727]  [] warn_slowpath_common+0x82/0xc0
[  107.963729]  [] warn_slowpath_null+0x1a/0x20
[  107.963731]  [] sg_rq_end_io+0x24e/0x340
[  107.963741]  [] ? add_timer_randomness+0xde/0x100
[  107.963745]  [] blk_finish_request+0x62/0xf0
[  107.963748]  [] scsi_end_request+0x106/0x1d0
[  107.963750]  [] scsi_io_completion+0x1b6/0x690
[  107.963752]  [] scsi_finish_command+0xcf/0x120
[  107.963754]  [] scsi_eh_flush_done_q+0xf5/0x140
[  107.963760]  [] ata_scsi_port_error_handler+0x599/0x770
[  107.963763]  [] ? ata_scsi_cmd_error_handler+0x11d/0x150
[  107.963765]  [] ata_scsi_error+0xa0/0xe0
[  107.963766]  [] scsi_error_handler+0xdb/0x8a0
[  107.963779]  [] ? __schedule+0x310/0x7b0
[  107.963781]  [] ? scsi_eh_get_sense+0x240/0x240
[  107.963788]  [] kthread+0xe5/0x100
[  107.963790]  [] ? kthread_create_on_node+0x1e0/0x1e0
[  107.963792]  [] ret_from_fork+0x3f/0x70
[  107.963794]  [] ? kthread_create_on_node+0x1e0/0x1e0
[  107.963795] ---[ end trace b723db66c786bceb ]---

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-109-generic 4.4.0-109.132
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Wed Jan 17 12:34:22 2018
HibernationDevice: RESUME=/dev/mapper/pc17--vg-swap_1
InstallationDate: Installed on 2018-01-17 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
IwConfig:
 lono wireless extensions.
 
 ens192no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic 
root=/dev/mapper/hostname--vg-root ro
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-109-generic N/A
 linux-backports-modules-4.4.0-109-generic  N/A
 linux-firmware 1.157.14
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2014
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/14/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Source Code to cause Failure"
   
https://bugs.launchpad.net/bugs/1743859/+attachment/5038389/+files/scsi_test.c

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

Title:
  SCSI subsystem Kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Version Signature
  Ubuntu 4.4.0-109.132-generic 4.4.98

  Attached is source code for sending a scsi command block to a sg
  device. When this is executed it causes a a seg fault with the stack
  dump that can been seen in the dmesg logs(see Below). The code worked
  until 4.4.0-98. It also continues to work on newer versions of ubuntu,
  such as Ubuntu 17.10 with the most up to date kernel 4.13.0.25.
  Please let me know if there is anything else information wise I can do
  help clarify this error. I have been able to replicate this on
  multiple hardware scenarios so I hope that the attached source code
  should be enough fo

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

The latest HWE kernel should be 4.13 based.

** No longer affects: linux (Ubuntu Xenial)

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs were buil

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

2018-01-17 Thread Eduardo Rudas

You welcome! I'm happy to help!

Tested, it resolves the bug. Thanks!!! You're the best!

Just to be sure it was the right testing kernel, the output of uname -a:

4.13.0-25-generic #29~lp1743269TwoCommits SMP Wed Jan 17 17:15:20 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  P-state not working in kernel 4.13

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

Bug description:
  I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm
  using Xubuntu 17.10 (Description:Ubuntu 17.10, Release:  17.10). I
  use tlp 1.0-1~artful in order to improve battery performance,
  particularly enabling the Intel P-state performance scaling. In
  Xubuntu 17.04 it worked flawlessly, but when I upgraded to 17.10 the
  processor doesn't scale anymore. I ran all the updates and it's not
  working. I also did a clean install using another hard drive and the
  problem persist.

  I searched the tlp forums and similar problems pointed to a kernel
  bug, so I'm filing this report.

  I tested different mainline kernels in order to see what kernel
  version is causing the problem:

  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

I removed the Zesty bug task since it is now EOL.  Does this bug still
happen with the latest HWE kernel for Xenial?


** No longer affects: linux (Ubuntu 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/1724120

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs were built into a 4.10.0-37-generic #41 test
  kernel and verified to fix the problem:

  a525108cf1cc14651602d678da38fa627a76a724
  e1073d1e7920946ac4776a619cc40668b9e1401b
  40692eb5eea209c2dd55857f44b4e1d7206e91d6
  e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d

[Kernel-packages] [Bug 1743799] Missing required logs.

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 1743799

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: trusty

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

Title:
  miscellanea/fwts_test causes reboot

Status in Provider for Plainbox - Checkbox:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

[Kernel-packages] [Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash

I built a test kernel with two commits d9018976cdb6 and 9d63f1766. The test 
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1742696

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix
  of Intel SPI bug on certain serial flash

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

Bug description:
  New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI
  bug in kernel Edit"

  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.

  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:

  intel-spi intel-spi: s25fl064k (8192 Kbytes)

  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10

  
  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."

  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

I built a test kernel with commit cfddd4c.  The test kernel can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1743746

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  4.13: unable to increase MTU configuration for GRE devices

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

Bug description:
  [Impact]
  GRE overlay networks can't carry traffic with MTU > 1500

  [Test Case]
  sudo add-apt-repository cloud-archive:pike
  sudo apt update
  sudo apt install openvswitch-switch
  sudo ovs-vsctl add-br br-tun
  sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre 
options:remote_ip=10.100.1.1

  gre_sys device will be configured with MTU 1472.

  sudo ip link set gre_sys mtu 65000

  will fail with EINVAL.

  [Regression Potential]

  [Bug Report]

  Under Linux 4.13 its not possible to configure GRE tunnel devices with
  a MTU larger than 1500; this impacts on Open vSwitch (which creates
  tunnel devices for GRE overlay networking) and the ip tools.

  The kernel will error with:

    gre_sys: Invalid MTU 65000 requested, hw max 1500

  The side effect of this is that if overlay networks are configured
  with high MTUs, the gre devices fragment the packets and networking is
  generally slow/broken.

  This is resolved as part of the upcoming 4.15 kernel under:

  
https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146

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

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

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

I built a test kernel with two commits 7d5905dc14a and b29c6ef7bb.  The test 
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1743269

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  P-state not working in kernel 4.13

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

Bug description:
  I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm
  using Xubuntu 17.10 (Description:Ubuntu 17.10, Release:  17.10). I
  use tlp 1.0-1~artful in order to improve battery performance,
  particularly enabling the Intel P-state performance scaling. In
  Xubuntu 17.04 it worked flawlessly, but when I upgraded to 17.10 the
  processor doesn't scale anymore. I ran all the updates and it's not
  working. I also did a clean install using another hard drive and the
  problem persist.

  I searched the tlp forums and similar problems pointed to a kernel
  bug, so I'm filing this report.

  I tested different mainline kernels in order to see what kernel
  version is causing the problem:

  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1743766] Missing required logs.

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 1743766

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

Title:
  reboot/IKVM problems on Ubuntu 14.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On the 3.13.0-52-generic #86-Ubuntu kernel server worked perfectly fine.
  To mitigate meltdown vulnerability updated kernel to 3.13.0-139-generic 
#188-Ubuntu.

  Approximately one hour after system boots I get this bug. I can`t access 
server via IKVM(ssh works fine).
  Also I got problem with server reboot. On "reboot" or "init 6" commands 
server halts. Only option is to reset server via IPMI. After server reseted and 
system boots, IKVM and reboot works as intended for approximately one hour. 
Then bug is repeated.

  linux-image-3.13.0-139-generic:
Installed: 3.13.0-139.188
Candidate: 3.13.0-139.188

  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

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

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

[Kernel-packages] [Bug 1743799] Re: miscellanea/fwts_test causes reboot

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

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

Title:
  miscellanea/fwts_test causes reboot

Status in Provider for Plainbox - Checkbox:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly

2018-01-17 Thread Andrea

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

Title:
  Trackpad doesn't work proprerly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the 
Elantech trackpad here the two files of the commands:
  1)
  the file was empty because the file doesn't exist

  2)
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1043:1bb0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) 
[8086:1901] (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Skylake PCIe 
Controller (x16) [1043:1bb0]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: fee00238  Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <256ns, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt+ ABWMgmt+
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete+, EqualizationPhase1+
 EqualizationPhase2+, EqualizationPhase3+, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture 
Model [8

[Kernel-packages] [Bug 1740972] Re: No external microphone be detected via headset jack on a dell machine

2018-01-17 Thread Igor Tarasov

Please see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740971/comments/3
for more info on this.

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

Title:
  No external microphone be detected via headset jack on a dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Plug a headset into the headset jack
  check external microphone

  Expected results: external microphone should wrok well

  Actual results: No external microphone be detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740972/+subscriptions

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

[Kernel-packages] [Bug 1740971] Re: Can't detect external headset via line-out jack on some Dell machines

2018-01-17 Thread Igor Tarasov

I have the same problem. The problem is in kernel 4.13 (4.13.0-26 to be
exact), since it has appeared as I've installed HWE update. I've tried
rebooting with kernel 4.10 and this problem was gone. I've collected the
data via ubuntu-bug (was unable to collect it via apport-collect for
some reason).

The problem is that both microphone and headphone ports do not detect
when the jack gets inserted or removed. So, if you had your headphones
connected at the boot time (or at resume time) system would always
consider jack inserted (and all sound control frontends, such as
pavucontrol, would report it as inserted). However, hdajacksensetest
reports jack state correctly.

The system changes jack status only on reboot or resume.

** Attachment added: "ubuntu-bug report"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740971/+attachment/5038351/+files/apport.linux-image-4.13.0-26-generic.qvwtvazv.apport

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

Title:
   Can't detect external headset via line-out jack on some Dell machines

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

Bug description:
  insert a headset to line-out jack

  Expected results: system should detect line-out port and sound output
  through line-out jack

  Actual results: Can't detect external headset via line-out jack

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740971/+subscriptions

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

[Kernel-packages] [Bug 1743158] Re: Trackpad doesn't work proprerly

2018-01-17 Thread Andrea

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

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

Title:
  Trackpad doesn't work proprerly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello everyone, my laptop is a asus rog gl503vm and I have an issue with the 
Elantech trackpad here the two files of the commands:
  1)
  the file was empty because the file doesn't exist

  2)
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5910] (rev 05)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1043:1bb0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

  00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) 
[8086:1901] (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Skylake PCIe 
Controller (x16) [1043:1bb0]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: fee00238  Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <256ns, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt+ ABWMgmt+
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete+, EqualizationPhase1+
 EqualizationPhase2+, EqualizationPhase3+, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:08.0 System peripheral [0880]: Intel Corporation Skylake Gaussian Mixture 
Model [8086:1911]
Subsyste

[Kernel-packages] [Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash

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

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

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

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

Title:
  Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix
  of Intel SPI bug on certain serial flash

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

Bug description:
  New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI
  bug in kernel Edit"

  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.

  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:

  intel-spi intel-spi: s25fl064k (8192 Kbytes)

  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10

  
  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."

  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  P-state not working in kernel 4.13

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

Bug description:
  I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm
  using Xubuntu 17.10 (Description:Ubuntu 17.10, Release:  17.10). I
  use tlp 1.0-1~artful in order to improve battery performance,
  particularly enabling the Intel P-state performance scaling. In
  Xubuntu 17.04 it worked flawlessly, but when I upgraded to 17.10 the
  processor doesn't scale anymore. I ran all the updates and it's not
  working. I also did a clean install using another hard drive and the
  problem persist.

  I searched the tlp forums and similar problems pointed to a kernel
  bug, so I'm filing this report.

  I tested different mainline kernels in order to see what kernel
  version is causing the problem:

  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  4.13: unable to increase MTU configuration for GRE devices

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

Bug description:
  [Impact]
  GRE overlay networks can't carry traffic with MTU > 1500

  [Test Case]
  sudo add-apt-repository cloud-archive:pike
  sudo apt update
  sudo apt install openvswitch-switch
  sudo ovs-vsctl add-br br-tun
  sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre 
options:remote_ip=10.100.1.1

  gre_sys device will be configured with MTU 1472.

  sudo ip link set gre_sys mtu 65000

  will fail with EINVAL.

  [Regression Potential]

  [Bug Report]

  Under Linux 4.13 its not possible to configure GRE tunnel devices with
  a MTU larger than 1500; this impacts on Open vSwitch (which creates
  tunnel devices for GRE overlay networking) and the ip tools.

  The kernel will error with:

    gre_sys: Invalid MTU 65000 requested, hw max 1500

  The side effect of this is that if overlay networks are configured
  with high MTUs, the gre devices fragment the packets and networking is
  generally slow/broken.

  This is resolved as part of the upcoming 4.15 kernel under:

  
https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146

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

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

[Kernel-packages] [Bug 474653] ✈The world's travel search engine Skyscanner compares millions of flights to find you the cheapest deal, fast.

2018-01-17 Thread shanta

Whether you want to go to Tenerife or Tokyo, we'll find low cost flights to
get you there.
We also find the cheapest hotels and car hire deals.
Just dial: 888-369-2751.
Skyscanner is free! When you find your flights and dial (888) 369-2751, we
redirect your call through directly to the airline or travel agent.We
never charge you commission. Nor do we add hidden fees. See more ways we put
you first.
Acclaimed flight comparison Skyscanner is an award winning site recommended
by: The Independent, The Guardian, Which? Travel, BBC Radio 1 and
more!Skyscanner has been consistently found to be comprehensive, fast,
and the best way to find cheap flights.
Just dial: 888-369-2751.
Let’s get social! Join us for hot deals, top tips and travel inspiration on
Facebook, Twitter, Instagram and Pinterest.
Find the perfect place to stay
The Trip by Skyscanner community has reviewed tens of thousands of hotels
around the world so you can always find the perfect place to stay, based on
your tribe and your price range.
Simply select your destination, dial 888-369-2751, and you are off!
And now Trip by Skyscanner searches all the top booking sites to make sure to
always find you the lowest price.
Check out some of our most popular destinations:
Chicago-New York$175.46Los Angeles-San Francisco$103.43Los Angeles-New York$175.77Chicago-Los Angeles$325.20Miami-New York$96.09Atlanta-Chicago$100.64Los Angeles-Manila$654.99New York City-Casablanca$825.17Miami-Johannesburg$1016.76Chicago-Minneapolis$95.85Atlanta-Orlando$90.65Chicago-Washington DC$195.64New York City-Toronto$119.47New York City-London$399.22Top Deal 55% Off:
Skyscanner's Flight Deals.
Primary: 888-369-2751. 24/7 Support.
Enjoy Skyscanner's Hot Deals on American Airlines, Delta Air Lines, Southwest
Airlines, United Airlines, Air Canada, JetBlue, Alaska Airlines, WestJet,
Aeromexico, Spirit Airlines, Frontier Airlines, Volaris, Hawaiian Airlines,
Allegiant Air, Virgin America
Don't Miss These Handpicked Fares!

Primary 888-369-2751. 24/7 Support

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

Title:
nvidia sound card test failure

Status in linux package in Ubuntu:
Fix Released
Status in linux-backports-modules-2.6.31 package in Ubuntu:
Fix Released

Bug description:
Upgrading to Karmic Using update manager. I lost the sound card.

ProblemType: Bug
Architecture: amd64
CheckboxCommand: gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 !
audioconvert ! audioresample ! gconfaudiosink'
CheckboxDescription:
Click the Test button to play a sound on the automatically detected playback
device.

Do you hear a sound?
CheckboxTest: playback_auto
Date: Wed Nov 4 11:55:29 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: python-gst0.10 0.10.17-1
ProcEnviron:
SHELL=/bin/bash
LANG=en_CA.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gst0.10-python
Tags: checkbox-bug
Uname: Linux 2.6.31-14-generic x86_64

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

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

[Kernel-packages] [Bug 1740971] Re: Can't detect external headset via line-out jack on some Dell machines

2018-01-17 Thread Launchpad Bug Tracker

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

** Changed in: linux-oem (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/1740971

Title:
   Can't detect external headset via line-out jack on some Dell machines

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  insert a headset to line-out jack

  Expected results: system should detect line-out port and sound output
  through line-out jack

  Actual results: Can't detect external headset via line-out jack

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740971/+subscriptions

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

[Kernel-packages] [Bug 1743812] Re: CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

2018-01-17 Thread dino99

We still wait for the compiler fixes
https://www.phoronix.com/scan.php?page=news_item&px=GCC-7.3-Release-Imminent

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm testing script:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/



  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [sudo] password for caravena: 
  Spectre and Meltdown mitigation detection tool v0.31

  Checking for vulnerabilities against running kernel Linux 4.13.0-30-generic 
#33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64
  CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz

  CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
  * Checking count of LFENCE opcodes in kernel:  YES 
  > STATUS:  NOT VULNERABLE  (114 opcodes found, which is >= 70, heuristic to 
be improved when official patches become available)

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
  *   Hardware (CPU microcode) support for mitigation
  * The SPEC_CTRL MSR is available:  NO 
  * The SPEC_CTRL CPUID feature bit is set:  NO 
  *   Kernel support for IBRS:  YES 
  *   IBRS enabled for Kernel space:  NO 
  *   IBRS enabled for User space:  NO 
  * Mitigation 2
  *   Kernel compiled with retpoline option:  NO 
  *   Kernel compiled with a retpoline-aware compiler:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
  * Kernel supports Page Table Isolation (PTI):  YES 
  * PTI enabled and active:  YES 
  * Checking if we're running under Xen PV (64 bits):  NO 
  > STATUS:  NOT VULNERABLE  (PTI mitigates the vulnerability)

  A false sense of security is worse than no security at all, see
  --disclaimer

  
  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1743766] Re: reboot/IKVM problems on Ubuntu 14.04

2018-01-17 Thread Brian Murray

** Tags added: regression-update

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

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

Title:
  reboot/IKVM problems on Ubuntu 14.04

Status in linux package in Ubuntu:
  New

Bug description:
  On the 3.13.0-52-generic #86-Ubuntu kernel server worked perfectly fine.
  To mitigate meltdown vulnerability updated kernel to 3.13.0-139-generic 
#188-Ubuntu.

  Approximately one hour after system boots I get this bug. I can`t access 
server via IKVM(ssh works fine).
  Also I got problem with server reboot. On "reboot" or "init 6" commands 
server halts. Only option is to reset server via IPMI. After server reseted and 
system boots, IKVM and reboot works as intended for approximately one hour. 
Then bug is repeated.

  linux-image-3.13.0-139-generic:
Installed: 3.13.0-139.188
Candidate: 3.13.0-139.188

  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

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

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

[Kernel-packages] [Bug 1743766] [NEW] reboot/IKVM problems on Ubuntu 14.04

2018-01-17 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

On the 3.13.0-52-generic #86-Ubuntu kernel server worked perfectly fine.
To mitigate meltdown vulnerability updated kernel to 3.13.0-139-generic 
#188-Ubuntu.

Approximately one hour after system boots I get this bug. I can`t access server 
via IKVM(ssh works fine).
Also I got problem with server reboot. On "reboot" or "init 6" commands server 
halts. Only option is to reset server via IPMI. After server reseted and system 
boots, IKVM and reboot works as intended for approximately one hour. Then bug 
is repeated.

linux-image-3.13.0-139-generic:
  Installed: 3.13.0-139.188
  Candidate: 3.13.0-139.188

Distributor ID: Ubuntu
Description:Ubuntu 14.04 LTS
Release:14.04
Codename:   trusty

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


** Tags: bot-comment regression-update trusty
-- 
reboot/IKVM problems on Ubuntu 14.04
https://bugs.launchpad.net/bugs/1743766
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 1742603] Re: Kernel 4.13.0-26.29~16.04.2 Causing Crash

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:

v4.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11
v4.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12
v4.13 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13

You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!

** Tags removed: pti
** Tags added: performing-bisect

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

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

Title:
  Kernel 4.13.0-26.29~16.04.2 Causing Crash

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Upgraded kernel to 4.13.0-26.29~16.04.2 and Cinnamon crashed while
  display was way off. As you can see in the system specs below, I
  booted into kernel 4.10 and all is well

  System:Host: Z97X-UD3H-BK Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 
5.4.0)
 Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
 Distro: Linux Mint 18.3 Sylvia
  Machine:   System: Gigabyte product: Z97X-UD3H-BK
 Mobo: Gigabyte model: Z97X-UD3H-BK-CF v: x.x
 Bios: American Megatrends v: F8 date: 09/19/2015
  CPU:   Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28000
 clock speeds: max: 3900 MHz 1: 897 MHz 2: 830 MHz 3: 1291 MHz
 4: 1061 MHz
  Graphics:  Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated 
Graphics Controller
 bus-ID: 00:02.0
 Card-2: NVIDIA GM206 [GeForce GTX 950] bus-ID: 01:00.0
 Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: 
fbdev,vesa,nouveau)
 Resolution: 2560x1440@59.95hz
 GLX Renderer: GeForce GTX 950/PCIe/SSE2
 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes
  Audio: Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
 driver: snd_hda_intel bus-ID: 00:03.0
 Card-2 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1
 Card-3 Intel 9 Series Family HD Audio Controller
 driver: snd_hda_intel bus-ID: 00:1b.0
 Card-4 Logitech HD Webcam C910 driver: USB Audio usb-ID: 003-003
 Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
  Network:   Card-1: Intel Ethernet Connection I217-V
 driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0
 IF: eno1 state: down mac: 
 Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter
 driver: ath9k bus-ID: 05:00.0
 IF: wlp5s0 state: up mac: 
  Drives:HDD Total Size: 2490.5GB (1.1% used)
 ID-1: /dev/sda model: Crucial_CT240M50 size: 240.1GB
 ID-2: /dev/sdb model: Samsung_SSD_850 size: 250.1GB
 ID-3: /dev/sdc model: WDC_WD1002FAEX size: 1000.2GB
 ID-4: /dev/sdd model: WDC_WD10EFRX size: 1000.2GB
  Partition: ID-1: / size: 23G used: 14G (63%) fs: ext4 dev: /dev/sdb1
 ID-2: /home size: 202G used: 6.5G (4%) fs: ext4 dev: /dev/sdb3
 ID-3: swap-1 size: 5.12GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:33C
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 218 Uptime: 29 min Memory: 1263.6/32009.9MB
 Init: systemd runlevel: 5 Gcc sys: 5.4.0
 Client: Shell (bash 4.3.481) inxi: 2.2.35

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

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

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Triaged

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

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

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

Title:
  P-state not working in kernel 4.13

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm
  using Xubuntu 17.10 (Description:Ubuntu 17.10, Release:  17.10). I
  use tlp 1.0-1~artful in order to improve battery performance,
  particularly enabling the Intel P-state performance scaling. In
  Xubuntu 17.04 it worked flawlessly, but when I upgraded to 17.10 the
  processor doesn't scale anymore. I ran all the updates and it's not
  working. I also did a clean install using another hard drive and the
  problem persist.

  I searched the tlp forums and similar problems pointed to a kernel
  bug, so I'm filing this report.

  I tested different mainline kernels in order to see what kernel
  version is causing the problem:

  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

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

This change was made by a bot.

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

** Tags added: artful

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm testing script:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/



  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [sudo] password for caravena: 
  Spectre and Meltdown mitigation detection tool v0.31

  Checking for vulnerabilities against running kernel Linux 4.13.0-30-generic 
#33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64
  CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz

  CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
  * Checking count of LFENCE opcodes in kernel:  YES 
  > STATUS:  NOT VULNERABLE  (114 opcodes found, which is >= 70, heuristic to 
be improved when official patches become available)

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
  *   Hardware (CPU microcode) support for mitigation
  * The SPEC_CTRL MSR is available:  NO 
  * The SPEC_CTRL CPUID feature bit is set:  NO 
  *   Kernel support for IBRS:  YES 
  *   IBRS enabled for Kernel space:  NO 
  *   IBRS enabled for User space:  NO 
  * Mitigation 2
  *   Kernel compiled with retpoline option:  NO 
  *   Kernel compiled with a retpoline-aware compiler:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
  * Kernel supports Page Table Isolation (PTI):  YES 
  * PTI enabled and active:  YES 
  * Checking if we're running under Xen PV (64 bits):  NO 
  > STATUS:  NOT VULNERABLE  (PTI mitigates the vulnerability)

  A false sense of security is worse than no security at all, see
  --disclaimer

  
  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2018-01-17 Thread Kevin Wong

CPU: Ryzen Threadripper 1920X
Ubuntu 16.04 LTS

Identical problems to the above. Agonizing, irritating, random, low-load
idle-state freezes. No issues while under heavy load.


My fixes:

Disabled c-states in the BIOS
Disabled ASLR in the BIOS
Disabled AMD Cool 'n Quiet in the BIOS.

Compiled a new kernel from source, (4.13.16) but with "Offload
RCU_callback processing" aka CONFIG_RCU_NOCB_CPU, chosen in the kernel
config.

I added "rcu_nocbs=0-23" to the "GRUB_CMDLINE_LINUX" parameter in
/etc/default/grub (and then ran "sudo update-grub"). "0-23", to cover
all 24 threads on the 12 core Ryzen,

Rebooted.

Only with all of those fixes (yep, all of them, tested every one of them
separately -- that took an eon -- have I finally gotten a stable system.

Zero issues now after 8 weeks. Let's hope that holds.

Haven't tried any kernel updates, though.

In addition to the above, I also consulted these references:


http://blog.programster.org/stabilizing-ubuntu-16-04-on-ryzen

http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen

http://blog.programster.org/how-to-disable-aslr

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, whic

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1743746

Title:
  4.13: unable to increase MTU configuration for GRE devices

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  GRE overlay networks can't carry traffic with MTU > 1500

  [Test Case]
  sudo add-apt-repository cloud-archive:pike
  sudo apt update
  sudo apt install openvswitch-switch
  sudo ovs-vsctl add-br br-tun
  sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre 
options:remote_ip=10.100.1.1

  gre_sys device will be configured with MTU 1472.

  sudo ip link set gre_sys mtu 65000

  will fail with EINVAL.

  [Regression Potential]

  [Bug Report]

  Under Linux 4.13 its not possible to configure GRE tunnel devices with
  a MTU larger than 1500; this impacts on Open vSwitch (which creates
  tunnel devices for GRE overlay networking) and the ip tools.

  The kernel will error with:

    gre_sys: Invalid MTU 65000 requested, hw max 1500

  The side effect of this is that if overlay networks are configured
  with high MTUs, the gre devices fragment the packets and networking is
  generally slow/broken.

  This is resolved as part of the upcoming 4.15 kernel under:

  
https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146

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

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

[Kernel-packages] [Bug 1743812] [NEW] CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

2018-01-17 Thread Cristian Aravena Romero

Public bug reported:

Hello,

I'm testing script:
https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/


:~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
[sudo] password for caravena: 
Spectre and Meltdown mitigation detection tool v0.31

Checking for vulnerabilities against running kernel Linux 4.13.0-30-generic 
#33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64
CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Checking count of LFENCE opcodes in kernel:  YES 
> STATUS:  NOT VULNERABLE  (114 opcodes found, which is >= 70, heuristic to be 
> improved when official patches become available)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Mitigation 1
*   Hardware (CPU microcode) support for mitigation
* The SPEC_CTRL MSR is available:  NO 
* The SPEC_CTRL CPUID feature bit is set:  NO 
*   Kernel support for IBRS:  YES 
*   IBRS enabled for Kernel space:  NO 
*   IBRS enabled for User space:  NO 
* Mitigation 2
*   Kernel compiled with retpoline option:  NO 
*   Kernel compiled with a retpoline-aware compiler:  NO 
> STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with retpoline 
> are needed to mitigate the vulnerability)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Kernel supports Page Table Isolation (PTI):  YES 
* PTI enabled and active:  YES 
* Checking if we're running under Xen PV (64 bits):  NO 
> STATUS:  NOT VULNERABLE  (PTI mitigates the vulnerability)

A false sense of security is worse than no security at all, see
--disclaimer


Regards,
--
Cristian

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

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


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

** Attachment added: "Captura de pantalla de 2018-01-17 13-16-33.png"
   
https://bugs.launchpad.net/bugs/1743812/+attachment/5038299/+files/Captura%20de%20pantalla%20de%202018-01-17%2013-16-33.png

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm testing script:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/



  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [sudo] password for caravena: 
  Spectre and Meltdown mitigation detection tool v0.31

  Checking for vulnerabilities against running kernel Linux 4.13.0-30-generic 
#33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64
  CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz

  CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
  * Checking count of LFENCE opcodes in kernel:  YES 
  > STATUS:  NOT VULNERABLE  (114 opcodes found, which is >= 70, heuristic to 
be improved when official patches become available)

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
  *   Hardware (CPU microcode) support for mitigation
  * The SPEC_CTRL MSR is available:  NO 
  * The SPEC_CTRL CPUID feature

[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc8


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

Title:
  Screen blank, audio choppy, system locked

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: inte

[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

Does this bug go away if you boot back into the prior 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/1742867

Title:
  Screen blank, audio choppy, system locked

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1465.175694] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 209

[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-17 Thread Seth Forshee

@André: I've updated the firmware in the package below. Can you test
this package and confirm it fixes the issue? Thanks!

http://people.canonical.com/~sforshee/lp1743279/linux-
firmware_1.157.16~pre201801170951_all.deb

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

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

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

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

** Changed in: linux-firmware (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: In Progress => Incomplete

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Incomplete

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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

[Kernel-packages] [Bug 1743427] Re: Black screen with iMac 2011 and ATI Radeon 6970M

2018-01-17 Thread Hans Matros

Thanks this kernel version can boot the system, but the performance of
the UI have a problem. Everything lags and also with youtube video's
there are a lot of frame drops.

dmesg | grep -i radeon
[1.371941] [drm] radeon kernel modesetting enabled.
[1.514874] fb: switching to radeondrmfb from EFI VGA
[1.573397] radeon :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=none
[1.809709] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[1.809713] radeon :01:00.0: GTT: 1024M 0x4000 - 
0x7FFF
[1.809815] [drm] radeon: 1024M of VRAM memory ready
[1.809817] [drm] radeon: 1024M of GTT memory ready.
[1.814783] [drm] radeon: dpm initialized
[1.815311] [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
[1.826451] radeon :01:00.0: WB enabled
[1.826455] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0x957e19e9
[1.826458] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0x178c14b1
[1.827205] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00072118 and cpu addr 0x5541d674
[1.827212] radeon :01:00.0: radeon: MSI limited to 32-bit
[1.827245] radeon :01:00.0: radeon: using MSI.
[1.827275] [drm] radeon: irq initialized.
[3.011583] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[4.023636] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[5.035688] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[6.047740] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[7.059790] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[8.071841] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[9.083890] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[   10.095939] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[   11.107990] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[   12.120038] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying 
to reset the VCPU!!!
[   12.139899] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving 
up!!!
[   12.139907] radeon :01:00.0: failed initializing UVD (-1).
[   13.148133] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
[   13.148179] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on GFX ring (-110).
[   13.148197] [drm:radeon_device_init [radeon]] *ERROR* ib ring test failed 
(-110).
[   13.208032] [drm] radeon atom DIG backlight initialized
[   13.208041] [drm] Radeon Display Connectors
[   14.405759] fbcon: radeondrmfb (fb0) is primary device
[   16.430012] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[   16.444306] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on 
minor 1
[  180.804054] radeon_dp_aux_transfer_native: 326 callbacks suppressed
[  193.072054] radeon_dp_aux_transfer_native: 326 callbacks suppressed

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

Title:
  Black screen with iMac 2011 and ATI Radeon 6970M

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear community!

  I have installed Ubuntu 17.10 (also tried 17.04 and 16.04), and the
  system gets a black screen on boot with all tested Ubuntu versions.
  Also ping and ssh to the host does not work. The fan's are running,
  the screen is black and nothing more.

  When i insert in Grub nomodeset, the system can boot.

  I have also tested Kernel 4.14 and 4.15RC7.

  Hardware Information:

  00:02.0 Display controller: Intel Corporation 2nd Generation Core
  Processor Family Integrated Graphics Controller (rev 09)

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Blackcomb [Radeon HD 6970M/6990M]

  
  Thanks for help or any hint.

  Best regards,

  Hans
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1756 F pulseaudio
   /dev/snd/controlC1:  christian   1756 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/storage-swap
  InstallationDate: Installed on 2018-01-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  MachineType: Apple Inc. iMac12,2
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 E

[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-17 Thread André Brait Carneiro Fabotti

AceLan, you can disconsider the last comment. I've found a way to use
mIRC on the web browser and I've contacted the Kernel team there.
They're already looking into this.

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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

[Kernel-packages] [Bug 1714112] Re: EDAC sbridge: Failed to register device with error -22.

2018-01-17 Thread Daniel Klockenkämper

I am seeing this problem still occuring in kernel 4.13.0-26-generic:

EDAC MC0: Giving out device to module sb_edac.c controller Haswell 
SrcID#1_Ha#0: DEV :ff:12.0 (INTERRUPT)
EDAC MC1: Giving out device to module sb_edac.c controller Haswell 
SrcID#0_Ha#0: DEV :7f:12.0 (INTERRUPT)
EDAC sbridge: Some needed devices are missing
EDAC MC: Removed device 0 for sb_edac.c Haswell SrcID#1_Ha#0: DEV :ff:12.0
Removed device 1 for sb_edac.c Haswell SrcID#0_Ha#0: DEV :7f:12.0
EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Couldn't find mci handler
EDAC sbridge: Failed to register device with error -19.

We can't apply actual HWE Kernel for Ubuntu 16.04 Server, since this bug
breaks our bridge networking for KVM, because of:

  * vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"

Will there be a Fix for HWE Kernels?

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

Title:
  EDAC sbridge: Failed to register device with error -22.

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  These kernel error messages appear with artful kernel
  4.12.0-11-generic.

  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Failed to register device with error -22.

  EDAC_GHES is enable in 4.12.0-11-generic, but according to
  https://lkml.org/lkml/2017/7/9/258 it should be disabled.

  $ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  CONFIG_EDAC_GHES=y
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

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

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

[Kernel-packages] [Bug 1742603] Re: Kernel 4.13.0-26.29~16.04.2 Causing Crash

2018-01-17 Thread Benedict Brown

My colleague who handles IT for the department and has been seeing this
on multiple computers reports the following:

I tried the mainline kernel 4.15-rc8 , no joy. Still getting the NULL
pointer Oops error.

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

Title:
  Kernel 4.13.0-26.29~16.04.2 Causing Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded kernel to 4.13.0-26.29~16.04.2 and Cinnamon crashed while
  display was way off. As you can see in the system specs below, I
  booted into kernel 4.10 and all is well

  System:Host: Z97X-UD3H-BK Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 
5.4.0)
 Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
 Distro: Linux Mint 18.3 Sylvia
  Machine:   System: Gigabyte product: Z97X-UD3H-BK
 Mobo: Gigabyte model: Z97X-UD3H-BK-CF v: x.x
 Bios: American Megatrends v: F8 date: 09/19/2015
  CPU:   Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28000
 clock speeds: max: 3900 MHz 1: 897 MHz 2: 830 MHz 3: 1291 MHz
 4: 1061 MHz
  Graphics:  Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated 
Graphics Controller
 bus-ID: 00:02.0
 Card-2: NVIDIA GM206 [GeForce GTX 950] bus-ID: 01:00.0
 Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: 
fbdev,vesa,nouveau)
 Resolution: 2560x1440@59.95hz
 GLX Renderer: GeForce GTX 950/PCIe/SSE2
 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes
  Audio: Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
 driver: snd_hda_intel bus-ID: 00:03.0
 Card-2 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1
 Card-3 Intel 9 Series Family HD Audio Controller
 driver: snd_hda_intel bus-ID: 00:1b.0
 Card-4 Logitech HD Webcam C910 driver: USB Audio usb-ID: 003-003
 Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
  Network:   Card-1: Intel Ethernet Connection I217-V
 driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0
 IF: eno1 state: down mac: 
 Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter
 driver: ath9k bus-ID: 05:00.0
 IF: wlp5s0 state: up mac: 
  Drives:HDD Total Size: 2490.5GB (1.1% used)
 ID-1: /dev/sda model: Crucial_CT240M50 size: 240.1GB
 ID-2: /dev/sdb model: Samsung_SSD_850 size: 250.1GB
 ID-3: /dev/sdc model: WDC_WD1002FAEX size: 1000.2GB
 ID-4: /dev/sdd model: WDC_WD10EFRX size: 1000.2GB
  Partition: ID-1: / size: 23G used: 14G (63%) fs: ext4 dev: /dev/sdb1
 ID-2: /home size: 202G used: 6.5G (4%) fs: ext4 dev: /dev/sdb3
 ID-3: swap-1 size: 5.12GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:33C
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 218 Uptime: 29 min Memory: 1263.6/32009.9MB
 Init: systemd runlevel: 5 Gcc sys: 5.4.0
 Client: Shell (bash 4.3.481) inxi: 2.2.35

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

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

[Kernel-packages] [Bug 1743204] Re: Segmentation fault in "apt --fix-broken install"

2018-01-17 Thread Otto

I also blacklisted it in '/etc/apt/apt.conf.d/01autoremove' and apt
update now also runs to completion without any errors.

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

Title:
  Segmentation fault in "apt --fix-broken install"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected: New installation of 'wine'

  Result: (See attached screenshot of the terminal.)
  The installation failed with unmet dependencies, so I entered "sudo apt 
--fix-broken install" and in the course of this dpkg encountered a segmentation 
fault:

  Unpacking linux-image-extra-4.13.0-25-generic (4.13.0-25.29) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb
 (--unpack):
   unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.13.0-25-generic.list-new': Operation 
not permitted
  Segmentation fault

  I have seen this before reported as a bug: 1742387

  As I cannot attach more than one file (why this?) I'm inserting the
  full terminal content here:

  sudo apt install wine-stable
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies.
   linux-image-generic : Depends: linux-image-extra-4.13.0-25-generic but it is 
not going to be installed
   wine-stable : Depends: wine64 (>= 2.0.2-2ubuntu1) but it is not going to be 
installed or
  wine32 (>= 2.0.2-2ubuntu1)
 Depends: wine64 (< 2.0.2-2ubuntu1.1~) but it is not going to 
be installed or
  wine32 (< 2.0.2-2ubuntu1.1~)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  11:20:56 [root@scotland] ~
  sudo apt --fix-broken install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
linux-image-extra-4.13.0-25-generic
  The following NEW packages will be installed
linux-image-extra-4.13.0-25-generic
  0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
  6 not fully installed or removed.
  Need to get 0 B/31.5 MB of archives.
  After this operation, 163 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 383838 files and directories currently installed.)
  Preparing to unpack 
.../linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb ...
  Unpacking linux-image-extra-4.13.0-25-generic (4.13.0-25.29) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-extra-4.13.0-25-generic_4.13.0-25.29_amd64.deb
 (--unpack):
   unable to create new file 
'/var/lib/dpkg/info/linux-image-extra-4.13.0-25-generic.list-new': Operation 
not permitted
  Segmentation fault

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.13.0.25.26
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  john   6019 F pulseaudio
   /dev/snd/controlC1:  john   6019 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jan 14 11:24:06 2018
  HibernationDevice: RESUME=UUID=53ca4e3e-a7f4-4969-ad38-429b38324fed
  InstallationDate: Installed on 2017-04-28 (260 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. EP45-DS4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=4cfb4fad-eedb-4de1-9dd6-b384d7bc18e0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-08 (66 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-DS4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd09/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-DS4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpa

[Kernel-packages] [Bug 1743541] Re: Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is offline

Sorry for not posting the tools packages.  It should be available now: 
http://kernel.ubuntu.com/~jsalisbury/lp1743541

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

Title:
  Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is
  offline

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-16 
04:58:48 ==
  Problem Description :
  =

  cpupower monitor fails to show stop states when cpu 0 is made offline.

  Testing :
  =
  root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# 

  root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop | stop | stop 
 0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.01

  Details :
  
  uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 
21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  OS : Ubuntu 18.04
  Machine : Witherspoon ( DD2.1) and Boston (DD.01)

  Patch :
  
  Patch that fixes the issue : 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  == Comment: #1 - VIPIN K. PARASHAR  - 2018-01-16 
05:09:40 ==
  (In reply to comment #0)

  > Patch :
  > 
  > Patch that fixes the issue :
  > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
  > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  $ git log dbdc468f35ee827 -1
  commit dbdc468f35ee827cab2753caa1c660bdb832243a
  Author: Abhishek Goel 
  Date:   Wed Nov 15 14:10:02 2017 +0530

  cpupower : Fix cpupower working when cpu0 is offline
  
  cpuidle_monitor used to assume that cpu0 is always online which is not
  a valid assumption on POWER machines. This patch fixes this by getting
  the cpu on which the current thread is running, instead of always using
  cpu0 for monitoring which may not be online.
  
  Signed-off-by: Abhishek Goel 
  Signed-off-by: Shuah Khan 
  $

  Commit dbdc468f3 is available with 4.15-rc2 onwards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1743541/+subscriptions

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

[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage

2018-01-17 Thread mostafa741

I hope this bug will be fixed soon, this bug preventing me from
switching to Linux it also affects Fedora 27

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

Title:
  System freeze on high memory usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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

[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-17 Thread André Brait Carneiro Fabotti

Hi there, AceLan,

I've subscribed you to this bug because of 1) I've noticed you reported
another bug, which had a fix submitted to xenial-proposed a few days
ago, and I'm looking for some guidance here on how to have this bug
fixed ASAP (even by me, if it means creating and submitting a new
package myself or something like that, as per Ubuntu's documentation on
fixing bugs) and 2) You're probably affected by it, if you own a QCA6174
and you're using a kernel later than 4.12.

I'd consider this bug a high priority one because it directly affects
users (and in a very significant way), it's been already fixed in
upstream since October 2017 and porting the fix to Ubuntu would be
trivial, I guess.

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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

[Kernel-packages] [Bug 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

I built the next test kernel, up to the following commit:
bf1d6b2c76eda86159519bf5c427b1fa8f51f733

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1742602

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

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

Bug description:
  I'm following the HWE kernels in Ubuntu 16.04, so my kernel was
  upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the
  splash screen and disk encryption passphrase prompt showed correctly,
  but when X started, the screen went blank. Logs showed everything
  running as normal despite the blank screen. Rebooting with the
  "nomodeset" kernel parameter fixed the issue but is not suitable as a
  permanent workaround since it disables my external monitor. Rebooting
  back into 4.10 also fixed the issue.

  I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried
  both intel and fbdev X drivers, both gave a blank screen.

  lsb_release: Ubuntu 16.04.3 LTS

  dpkg-query -W:

  linux-signed-image-generic-hwe-16.04  4.13.0.26.46
  xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1
  xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1
  xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1

  In Xorg.0.log with fbdev, I saw:

  [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument

  repeated 239 times.

  Typical kernel messages attached (from kern.log, reformatted to look
  like dmesg).

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

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

[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

2018-01-17 Thread Scott Moser

Hi,

I'm coming here from bug 1730744.
Is this bug expected to be fixed for 18.04?

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

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

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

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

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

  ### To run the test ###

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot