date:20180410

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1752655

Title:
  retpoline: ignore %cs:0xNNN constant indirections

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

Bug description:
  These are paravirt style indirections and can be ignored.

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

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

[Kernel-packages] [Bug 1755804] Re: IMA policy parsing is broken in 4.13

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1755804

Title:
  IMA policy parsing is broken in 4.13

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

Bug description:
  
  == SRU Justification ==
  Artful has a bug in IMA policy parsing introduced by mailine commit 
787d8c530af7.  
  This bug prevents setting IMA measurements and appraisal options per fsuuid.

  This commit has been cc'd to upstream stable.  However, it has not yet been 
applied
  to Artful, since upstream 4.13 is EOL.

  == Fix ==
  36447456e1cc ("ima/policy: fix parsing of fsuuid")

  == Regression Potential ==
  Low. This patch has also been sent to upstream stable, so it has had 
additional upstream
  review.

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




  
  Linux kernel version 4.13 has a bug in IMA policy parsing that prevents 
setting IMA measurements and appraisal options per fsuuid.

  The issue can be reproduced with simple ima_policy:

  # fsuuid=$(blkid -s UUID -o value /dev/sda1)
  # cat > ima_policy << EOF
  dont_appraise fsuuid=$fsuuid
  dont_measure fsuuid=$fsuuid
  EOF
  # cat ima_policy > /sys/kernel/security/ima/policy
  cat: write error: Invalid argument
  # dmesg | tail
  [  928.069606] audit: type=1805 audit(1521031959.907:18): 
action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=0
  [  928.069895] audit: type=1802 audit(1521031959.908:19): pid=1806 uid=0 
auid=0 ses=1 op="update_policy" cause="invalid-policy" comm="cat" res=0
  [  928.070829] IMA: policy update failed
  [  928.070860] audit: type=1802 audit(1521031959.909:20): pid=1806 uid=0 
auid=0 ses=1 op="policy_update" cause="failed" comm="cat" res=0

  The same policy can be successfully loaded on v4.10:

  (v4.10) # dmesg | tail
  [   54.071383] IMA: policy update completed
  [   54.071484] kauditd_printk_skb: 1 callbacks suppressed
  [   54.071487] audit: type=1805 audit(1521030962.958:15): 
action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1
  [   54.071491] audit: type=1805 audit(1521030962.958:16): 
action="dont_measure" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1
  [   54.071493] audit: type=1802 audit(1521030962.958:17): pid=1793 uid=0 
auid=0 ses=1 op="policy_update" cause="completed" comm="cat" res=1

  The bug is fixed in the mainline kernel:

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/security/integrity/ima/ima_policy.c?id=36447456e1cca853188505f2a964dbbeacfc7a7a
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 14 12:37 seq
   crw-rw 1 root audio 116, 33 Mar 14 12:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro console=tty1 console=ttyS0 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias:

[Kernel-packages] [Bug 1758364] Re: add audio kernel patches for Raven

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1758364

Title:
  add audio kernel patches for Raven

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

Bug description:
  [impact]
  Raven platforms don't have audio support.

  Please include these patches in the OEM and HWE kernels for Raven
  platforms:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/pci/hda?h=v4.14.28=ca90f34e2e80597dee73c2e8d55de364a34c112b
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/sound/pci/hda?h=v4.14.28=b177556318a731878a1e9e8a9bb28b98f7bc832c

  [test case]
  boot a kernel with the backported commits on such a system, test that audio 
works.

  [regression potential]
  none, they just add a pci-id and fix a typo

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

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

[Kernel-packages] [Bug 1755979] Re: Cpu utilization showing system time for kvm guests (performance) (sysstat)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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

** Tags added: verification-needed-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/1755979

Title:
Cpu utilization showing system time for kvm guests (performance)
(sysstat)

Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux source package in Bionic:
Fix Committed

Bug description:
== SRU Justification ==
All KVM guest cpu utilization is being reported as sys% time in the host.
It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has
been broken since v4.13 by commit 8b24e69fc47e436.

Commit 61bd0f66ff92 fixes this bug and is included in mainline as of
v4.16-rc5.
The commit was cc'd to upstream stable, but has not yet landed in upstream
4.15.

== Fix ==
61bd0f66ff92 ("KVM: PPC: Book3S HV: Fix guest time accounting with
VIRT_CPU_ACCOUNTING_GEN")

== Regression Potential ==
Low. Also cc'd to stable, so it has had additionl upstream review. Limited
to powerpc.

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

== Comment: #0 - JENIFER HOPPER - 2018-03-14 16:20:47 ==
+++ This bug was initially created as a clone of Bug #163375 +++

---Problem Description---
All KVM guest cpu utilization is being reported as sys% time in the host.
It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has been
broken since v4.13 by commit:

commit 8b24e69fc47e43679bb29ddb481aa0e8dce2a3c5
Author: Paul Mackerras
Date: Mon Jun 26 15:45:51 2017 +1000

KVM: PPC: Book3S HV: Close race with testing for signals on guest
entry

---

That is now fixed and upstream accepted in Paulus' tree as git commit:

https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-fixes=61bd0f66ff92d5ce765ff9850fd3cbfec773c560
("KVM: PPC: Book3S HV: Fix guest time accounting with
VIRT_CPU_ACCOUNTING_GEN")

Please include this patch in Ubuntu so that guest cpu accounting is
correct.

Contact Information = jhop...@us.ibm.com

---uname output---
Linux ltc-b114 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018
ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 5104-22C

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

---Steps to Reproduce---
Start a KVM guest, run something that generates cpu utilization in the
guest, observe mpstat on the host.

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

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

[Kernel-packages] [Bug 1755954] Re: external mic not work on Dell OptiPlex 7460 AIO

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1755954

Title:
  external mic not work on Dell OptiPlex 7460 AIO

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  == SRU Justification ==
  We have a OEM bug #1727951, in this bug, The Dell OptiPlex 7460 AIO can't
  detect external mic and can't record sound via external mic. After applying
  the fixup of ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, the problem can be fixed.

  == Fix ==
  40e2c4e5("iALSA: hda/realtek - Add headset mode support for Dell laptop")

  == Regression Potential ==
  very low, since this patch only applies to specific Dell machines which have 
subsystem id: 1028084b and 1028084e.

  
  == Test Case ==
  plug the headset and record the sound on this machine, we can see the
  external mic in the sound-setting and can record sound through this mic.

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

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

[Kernel-packages] [Bug 1755595] Re: sbsa watchdog crashes thunderx2 system

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1755595

Title:
  sbsa watchdog crashes thunderx2 system

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

Bug description:
  [Impact]
  Using the SBSA watchdog will crash the OS on ThunderX2 systems. This is not 
an issue in current firmware because the SBSA watchdog is not exposed - but it 
is likely to be introduced in a future update.

  [Test Case]
  $ sudo bash
  # cat < /dev/watchdog

  [Regression Risk]
  The fix is restricted the sbsa_gwdt driver, which is only currently available 
on some arm64 servers.

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

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

[Kernel-packages] [Bug 1758471] Re: apparmor: fix bad __initdata tagging on, apparmor_initialized

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-xenial

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

Title:
  apparmor: fix bad __initdata tagging on, apparmor_initialized

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

Bug description:
  When building the Xenial kernel we get the following warning

  WARNING: vmlinux.o(.text+0x393a60): Section mismatch in reference from
  the function param_set_aauint() to the variable
  .init.data:apparmor_initialized

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

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

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

2018-04-10 Thread Clément Gayot

Partial solution found !

After three months of research, I came by chance on this website :
https://hive.blasux.ru/u/Stiletto/G752

# cd /sys/bus/hid/drivers/hid-multitouch
# ls
0018:04F3:3043.0007 bind module new_id uevent unbind
# echo "0018:04F3:3043.0007" > unbind
# echo 0018 04F3 3043 0013 > new_id

With libinput-devices, two devices are now listed :
ELAN1203:00 04F3:3043 Mouse
ELAN1203:00 04F3:3043 Touchpad

Touchpad mouse and buttons works, but no solution for multitouch (no
gesture capabilities for Elan Mouse on kernel 4.15). I continue my
research in relation to that.

You can make this persistent by creating a service that launch a bash
script with these commands on OS startup.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [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)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S:

[Kernel-packages] [Bug 1762709] 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 1762709

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

Title:
  Unable to fetch git repos using autotest framework with Bionic kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  All the tests that need to fetch a git repo for testing failed with error 
message like: 
  CmdError: Command https://github.com/tytso/xfstests-bld> 
failed, rc=128, Command returned non-zero exit status
  * Command: 
  git clone https://github.com/tytso/xfstests-bld
  Exit status: 128
  Duration: 0.254368066788
   
  stderr:
  Cloning into 'xfstests-bld'...
  fatal: unable to access 'https://github.com/tytso/xfstests-bld/': 
gnutls_handshake() failed: An unexpected TLS packet was received.

  If you fetch this repo manually it will work (even with proxy configured)
  This needs to be investigated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Apr 10 11:35:24 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

--- Comment From bssrika...@in.ibm.com 2018-04-10 06:53 EDT---
We have got the qemu build with htm-on today [April 10th]. Now we are able to 
start compat mode guests with htm-on.. apart from bug 166570 things look good. 
We can close this one.

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name

[Kernel-packages] [Bug 1761443] Re: linux-aws: 4.4.0-1055.64 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761443/+subscriptions

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

[Kernel-packages] [Bug 1762500] Re: ADT security test on linux fails because /proc/self/stack shows 0

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

The error message has been addressed in bug 1758242, which is also a dup
of bug 1751202


** This bug has been marked a duplicate of bug 1751202
   test_095_kernel_symbols_missing in ubuntu_qrt_kernel_security failed on 
Bionic

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

Title:
  ADT security test on linux fails because /proc/self/stack shows 0

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

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-bionic/bionic/i386/l/linux/20180409_125745_f671c@/log.gz

  ==
  FAIL: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
  kernel addresses in kallsyms and modules are zeroed out
  --
  Traceback (most recent call last):
File "./test-kernel-security.py", line 1521, in 
test_095_kernel_symbols_missing
  self._check_pK_files(expected)
File "./test-kernel-security.py", line 1496, in _check_pK_files
  expected, retry=True)
File "./test-kernel-security.py", line 1378, in _read_twice
  self.assertFalse(0 == int(address, 16), "%s: root saw %s" % (filename, 
address))
  AssertionError: /proc/self/stack: root saw 0


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

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

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

[Kernel-packages] [Bug 1761438] Re: linux: 4.4.0-120.144 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
  derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
+ bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

Title:
  linux: 4.4.0-120.144 -proposed tracker

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

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

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

  backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
  derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761438/+subscriptions

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

[Kernel-packages] [Bug 1762672] 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/1762672

Title:
  TPM on Dell XPS 13 stopped working after upgrade to 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1761439] Re: linux-aws: 4.4.0-1017.17 -proposed tracker

4.4.0-1017.17 - aws
Regression test CMPL.

Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only 
spotted on t2.small, passed on the rest
  ubuntu_kvm_unit_tests - test skipped, KVM not supported

Skipped / blacklisted:
 * ubuntu_aufs_smoke_test
 * ubuntu_fan_smoke_test
 * ubuntu_kernel_selftests
 * ubuntu_loop_smoke_test
 * ubuntu_ltp
 * ubuntu_lttng_smoke_test
 * ubuntu_stress_smoke_test
 * ubuntu_sysdig_smoke_test
 * ubuntu_unionmount_overlayfs_suite
 * ubuntu_zfs_smoke_test
 * ubuntu_zram_smoke_test

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

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

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

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

** Tags added: regression-testing-passed

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761439/+subscriptions

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

[Kernel-packages] [Bug 1762652] Re: perf DWARF unwind failed

2018-04-10 Thread Paul White

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

Title:
  perf DWARF unwind failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10. To reproduce:

  $ perf test
  [...]
  57: DWARF unwind   : FAILED!
  [...]

  It seems perf is somehow mis-configured.

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

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

[Kernel-packages] [Bug 1762695] 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 1762695

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

Title:
  Backport USB core quirks

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ===SRU Justification===
  [Impact]
  Currently we need to recompile the entire kernel if we want try quirks
  in usbcore.

  [Test]
  Use kernel parameter "usbcore.quirks=" in conjunction with dynamic debug
  for usbcore, we can see that usb quirks successfully enabled for USB
  devices dynamically.
   
  [Fix]
  Introduce a new module parameter, "usbcore.quirks=". Users now can try
  different quirks without compiling anything.

  [Regression Potential]
  Low. It doesn't change any behavior of usb driver per se, it simply adds
  new logic to detect quirks.

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

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

[Kernel-packages] [Bug 1762693] 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/1762693

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my computer boots with the most recent kernel 4.13.0-38-generic,
  I don't have a working network connection. ethtool reports that my
  network interface doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt 
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Full 
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Full 
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
 drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  115.022823] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  120.800524] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  120.910537] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  125.019509] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  131.040530] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  131.164741] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  136.039268] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  142.048536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  142.186891] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  147.038361] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500

  Everything works fine when I boot Linux 4.13.0-37-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-04-10 Thread seanlano

I've followed the step linked to in
https://bugs.freedesktop.org/show_bug.cgi?id=104990 and have found that
using 'libinput measure touchpad-pressure --touch-thresholds=105:60
--palm-threshold=230' seemed to work well.

I was not able to format it into the hwdb file, however, so couldn't
actually test it on my machine.

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Confirmed
Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

[Kernel-packages] [Bug 1757937] Re: zram smoke test failed on GCP 4.13 / AWS 4.15, 4.4

Patch to blacklist these on GCP / AWS has been applied.

http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=40916a0680295d860c09d4c884d4aa86e3853d18
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=81862bb97d80bf48f6349e21e259475462663f0d

We can close this now.

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

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  zram smoke test failed on GCP 4.13 / AWS 4.15, 4.4

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  The zram smoke test failed due to the absence of the zram module.

  modprobe: FATAL: Module zram not found in directory
  /lib/modules/4.13.0-1012-gcp

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

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

[Kernel-packages] [Bug 1762709] [NEW] Unable to fetch git repos using autotest framework with Bionic kernel

Public bug reported:

All the tests that need to fetch a git repo for testing failed with error 
message like: 
CmdError: Command https://github.com/tytso/xfstests-bld> failed, 
rc=128, Command returned non-zero exit status
* Command: 
git clone https://github.com/tytso/xfstests-bld
Exit status: 128
Duration: 0.254368066788
 
stderr:
Cloning into 'xfstests-bld'...
fatal: unable to access 'https://github.com/tytso/xfstests-bld/': 
gnutls_handshake() failed: An unexpected TLS packet was received.

If you fetch this repo manually it will work (even with proxy configured)
This needs to be investigated.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu4
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
CurrentDmesg:
 
Date: Tue Apr 10 11:35:24 2018
HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-15-generic N/A
 linux-backports-modules-4.15.0-15-generic  N/A
 linux-firmware 1.173
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Summary changed:

- Unable to fetch git repos with autotest infrastructure with Bionic kernel
+ Unable to fetch git repos using autotest framework with Bionic 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/1762709

Title:
  Unable to fetch git repos using autotest framework with Bionic kernel

Status in linux package in Ubuntu:
  New

Bug description:
  All the tests that need to fetch a git repo for testing failed with error 
message like: 
  CmdError: Command https://github.com/tytso/xfstests-bld> 
failed, rc=128, Command returned non-zero exit status
  * Command: 
  git clone https://github.com/tytso/xfstests-bld
  Exit status: 128
  Duration: 0.254368066788
   
  stderr:
  Cloning into 'xfstests-bld'...
  fatal: unable to access 'https://github.com/tytso/xfstests-bld/': 
gnutls_handshake() failed: An unexpected TLS packet was received.

  If you fetch this repo manually it will work (even with proxy configured)
  This needs to be investigated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Apr 10 11:35:24 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list:

[Kernel-packages] [Bug 1762709] Re: Unable to fetch git repos using autotest framework with Bionic kernel

On a second thought, since it works with proxy configured from the
shell, RT ticket might not be helpful on this.

This looks like an issue in some package.

ubuntu@kernel02:/tmp$ if echo "" | nc -w 2 squid.internal 3128 >/dev/null 2>&1; 
then
> echo "Running in the Canonical CI environment"
> export http_proxy="http://squid.internal:3128;
> export https_proxy="http://squid.internal:3128;
> elif echo "" | nc -w 2 91.189.89.216 3128 >/dev/null 2>&1; then
> echo "Running in the Canonical enablement environment"
> export http_proxy="http://91.189.89.216:3128;
> export https_proxy="http://91.189.89.216:3128;
> elif echo "" | nc -w 2 10.245.64.1 3128 >/dev/null 2>&1; then
> echo "Running in the Canonical enablement environment"
> export http_proxy="http://10.245.64.1:3128;
> export https_proxy="http://10.245.64.1:3128;
> fi
Running in the Canonical CI environment
ubuntu@kernel02:/tmp$ echo $https_proxy
http://squid.internal:3128
ubuntu@kernel02:/tmp$ git clone https://github.com/tytso/xfstests-bld
Cloning into 'xfstests-bld'...
remote: Counting objects: 6435, done.
remote: Compressing objects: 100% (80/80), done.
remote: Total 6435 (delta 51), reused 96 (delta 43), pack-reused 6309
Receiving objects: 100% (6435/6435), 4.78 MiB | 1.66 MiB/s, done.
Resolving deltas: 100% (3943/3943), done.

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

Title:
  Unable to fetch git repos using autotest framework with Bionic kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  All the tests that need to fetch a git repo for testing failed with error 
message like: 
  CmdError: Command https://github.com/tytso/xfstests-bld> 
failed, rc=128, Command returned non-zero exit status
  * Command: 
  git clone https://github.com/tytso/xfstests-bld
  Exit status: 128
  Duration: 0.254368066788
   
  stderr:
  Cloning into 'xfstests-bld'...
  fatal: unable to access 'https://github.com/tytso/xfstests-bld/': 
gnutls_handshake() failed: An unexpected TLS packet was received.

  If you fetch this repo manually it will work (even with proxy configured)
  This needs to be investigated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Apr 10 11:35:24 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

2018-04-10 Thread Dan Streetman

Due to the nature of this bug, being very difficult to reproduce, real 
verification could take weeks instead of only days.  However, one reporter has 
been running with a test kernel I built here
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1723127

which is the base 4.4.0-112 kernel plus the two patches from this bug.
In their testing, running on 6 weeks now, the problem has not reproduced
and they have seen no other issues.  Of course, that test kernel doesn't
have all the other patches that the -proposed kernel has, but that
testing is likely the best verification we can get for this particular
bug.  I have also asked the same reporter to switch their testing from
my test kernel over to the -proposed kernel, and to report any
unexpected issues they see.  If they do report any regression, I'll
communicate that here.

Based on that justification, I'll mark this bug as verified.

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

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

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [impact]

  The i40e driver sometimes causes a "malicious device" event that the
  firmware detects, which causes the firmware to reset the nic, causing
  an interruption in the network connection - which can cause further
  problems, e.g. if the interface is in a bond; the reset will at least
  cause a temporary interruption in network traffic.

  [fix]

  The upstream patch to fix this adjusts how the driver fragments TX
  data; the "malicious driver" detected by the firmware is a result of
  incorrectly crafted TX fragment descriptors (the firmware has specific
  complicated restrictions on this).  The patch is from Intel, and they
  suggested this specific patch to address the problem; additionally I
  have checked with someone who reported this to me and provided a test
  kernel with the patch to them, and they have been able to run ~6 weeks
  so far without reproducing the issue; previously they could reproduce
  it as quickly as a day, but usually within 2-3 weeks.

  [test case]

  the bug is unfortunately very difficult to reproduce, but as shown in
  this (and previous) bug comments, some users of the i40e have traffic
  that can consistently reproduce the problem (although usually on the
  order of days, or longer, to reproduce).  Reproducing is easily
  detected, as the nw traffic will be interrupted and the system logs
  will contain a message like:

  i40e :02:00.1: TX driver issue detected, PF reset issued

  [regression potential]

  the patch for this alters how tx is fragmented by the driver, so a
  possible regression would likely cause problems in TX traffic and/or
  additional "malicious device detection" events.


  [original description]

  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

[Kernel-packages] [Bug 1750349] Re: [Hyper-V] include kvp fix for Avoid reading past allocated blocks from KVP file

2018-04-10 Thread Chris Valean

The change is looking fine in artful proposed 4.13.0.39.42 kernel. bug
status changed to verification-done

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

Title:
  [Hyper-V] include kvp fix for Avoid reading past allocated blocks from
  KVP file

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  This commit is being requested in Bionic and linux-azure by Microsoft.  It 
has 
  already been applied to Bionic.  It is being requested in Artful, so it makes
  it's way into linux-azure through the re-base process.

  This fix is required if a large number of records are injected into a pool, 
  which can cause the kvp daemon to crash.

  This commit has been cc'd to upstream stable.  However, it has not yet been 
applied
  to Artful, since upstream 4.13 is EOL.

  == Fix ==
  297d6b6e56c2 ("hv: kvp: Avoid reading past allocated blocks from KVP file")

  == Regression Potential ==
  Low. This patch has also been sent to upstream stable, so it has had 
additional upstream
  review.

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

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

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

[Kernel-packages] [Bug 1762693] [NEW] No network with e1000e driver on 4.13.0-38-generic

2018-04-10 Thread Martin von Wittich

Public bug reported:

When my computer boots with the most recent kernel 4.13.0-38-generic, I
don't have a working network connection. ethtool reports that my network
interface doesn't have a connection:

martin@dogmeat ~ % cat ethtool.txt 
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: no

dmesg contains suspicious e1000e error messages:

martin@dogmeat ~ % tail -n 40 dmesg.txt
[   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
[   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
[   20.211717] Error parsing options; rc = [-2]
[   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[   51.244686] ahci :00:17.0: port does not support device sleep
[   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[  110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[  115.022823] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[  120.800524] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[  120.910537] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[  125.019509] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[  131.040530] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[  131.164741] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[  136.039268] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
[  142.048536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
None
[  142.186891] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
[  147.038361] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500

Everything works fine when I boot Linux 4.13.0-37-generic.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-38-generic 4.13.0-38.43
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  martin 2756 F pulseaudio
CurrentDesktop: MATE
Date: Tue Apr 10 11:34:19 2018
EcryptfsInUse: Yes
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine:

[Kernel-packages] [Bug 1758375] Re: efifb broken on ThunderX-based Gigabyte nodes

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1758375

Title:
  efifb broken on ThunderX-based Gigabyte nodes

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

Bug description:
  [Impact]
  The following error is reported on boot:

  [6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for
  efifb!

  This results in the efifb not being activated at boot. On this
  platform, the same device will be  initialized by the astdrmfb driver
  later in boot, so this isn't fatal, so the real SRU justification here
  is getting rid of the error message. It is possible that there are
  platforms where the efifb is behind a PCI bridge, and there is no
  accelerated alternative that will load later. This (theoretical) issue
  is most likely to impact d-i installs, where only a subset of fb
  drivers are included.

  [Test Case]
  dmesg | grep "failed to claim resource for efifb"

  [Regression Risk]
  The fix for this has been upstream since v4.14 with no known regressions. The 
driver is only used on EFI systems, which limits the risk to a subset of 
x86/ARM platforms. Regression tested on a Dell PowerEdge T610 (x86/UEFI).

  I have a test fix in ppa:dannf/efifb for regression testing.

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

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

[Kernel-packages] [Bug 1752655] Re: retpoline: ignore %cs:0xNNN constant indirections

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1752655

Title:
  retpoline: ignore %cs:0xNNN constant indirections

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

Bug description:
  These are paravirt style indirections and can be ignored.

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

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

[Kernel-packages] [Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

2018-04-10 Thread Hui Wang

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

Title:
  Let headset-mode initialization be called on Dell Precision 3930

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.

  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.

  [Test Case]
  plug the headset and play or record the sound on this machine, both playing
  and recording work well.

  [Fix]
  one commit from mainline kernel.

  [Regression Potential]
  very low, since this patch only applies to the specific Dell machine 
Precision 3930.

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

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

[Kernel-packages] [Bug 1755804] Re: IMA policy parsing is broken in 4.13

2018-04-10 Thread rppt

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

Title:
  IMA policy parsing is broken in 4.13

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

Bug description:
  
  == SRU Justification ==
  Artful has a bug in IMA policy parsing introduced by mailine commit 
787d8c530af7.  
  This bug prevents setting IMA measurements and appraisal options per fsuuid.

  This commit has been cc'd to upstream stable.  However, it has not yet been 
applied
  to Artful, since upstream 4.13 is EOL.

  == Fix ==
  36447456e1cc ("ima/policy: fix parsing of fsuuid")

  == Regression Potential ==
  Low. This patch has also been sent to upstream stable, so it has had 
additional upstream
  review.

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




  
  Linux kernel version 4.13 has a bug in IMA policy parsing that prevents 
setting IMA measurements and appraisal options per fsuuid.

  The issue can be reproduced with simple ima_policy:

  # fsuuid=$(blkid -s UUID -o value /dev/sda1)
  # cat > ima_policy << EOF
  dont_appraise fsuuid=$fsuuid
  dont_measure fsuuid=$fsuuid
  EOF
  # cat ima_policy > /sys/kernel/security/ima/policy
  cat: write error: Invalid argument
  # dmesg | tail
  [  928.069606] audit: type=1805 audit(1521031959.907:18): 
action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=0
  [  928.069895] audit: type=1802 audit(1521031959.908:19): pid=1806 uid=0 
auid=0 ses=1 op="update_policy" cause="invalid-policy" comm="cat" res=0
  [  928.070829] IMA: policy update failed
  [  928.070860] audit: type=1802 audit(1521031959.909:20): pid=1806 uid=0 
auid=0 ses=1 op="policy_update" cause="failed" comm="cat" res=0

  The same policy can be successfully loaded on v4.10:

  (v4.10) # dmesg | tail
  [   54.071383] IMA: policy update completed
  [   54.071484] kauditd_printk_skb: 1 callbacks suppressed
  [   54.071487] audit: type=1805 audit(1521030962.958:15): 
action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1
  [   54.071491] audit: type=1805 audit(1521030962.958:16): 
action="dont_measure" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1
  [   54.071493] audit: type=1802 audit(1521030962.958:17): pid=1793 uid=0 
auid=0 ses=1 op="policy_update" cause="completed" comm="cat" res=1

  The bug is fixed in the mainline kernel:

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/security/integrity/ima/ima_policy.c?id=36447456e1cca853188505f2a964dbbeacfc7a7a
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 14 12:37 seq
   crw-rw 1 root audio 116, 33 Mar 14 12:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro console=tty1 console=ttyS0 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1758800] Re: hda driver initialization takes too much time on the machine with coffeelake audio controller [8086:a348]

2018-04-10 Thread Hui Wang

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

Title:
  hda driver initialization takes too much time on the machine with
  coffeelake audio controller [8086:a348]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]

  We have a couple of laptop and desktop computers, all of them are cfl 
platforms
  and all of them have cfl audio controller [8086:a348], and these computers 
have
  different realtek codecs on them (alc256, alc255, alc289 and ...). The hda
  driver takes too much time (3 secs - 8 secs) to initialize on these machines.
  This problem never happened on kbl, skl, bdw, ... before.

  Sometimes this can make pulseaudio can't work well.

  pulseaudio starts, but the driver (as kernel modules) initialization has not
  finished, then there is no valid sink in the pulseaudio. At this moment, some 
UI
  Apps already start using pulseaudio to play sound, but users can't hear the 
sound
  as expected. This problem never happened before, it is exposed on cfl 
platforms,
  and all cfl platforms (with audio controller 8086:a348) have this problem.

  [Fix]
  Set the polling mode can fix this problem, and this workaround is in the
  mainline kernel.

  [Test Case]
  Boot the machine and check the dmesg, from the hda log, we can see the driver
  initialization is finished within 0.1s and pulseaudio works well.

  [Regression Potential]
  No regression, this fix is only for CFL audio controller (8086:a348), and
  in theory, polling mode is safe for all audio controllers, using interrupt
  mode rather than polling mode on other platforms just wants to save polling
  overhead for CPUs, since interrupt mode can't work well on CFL platform, we
  have to use polling mode.

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

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

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

--- Comment From iranna.an...@in.ibm.com 2018-04-10 06:42 EDT---
I think we are good to close this tracker bugzilla, given that all requested 
KVM fixes are now available with 4.15.0-15.16 and above.

Thank 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/1758910

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1762709] Re: Unable to fetch git repos using autotest framework with Bionic kernel

Tested with an older kernel on the same s390x node (kernel02), this
issue still exists.

Must be something else.

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

Title:
  Unable to fetch git repos using autotest framework with Bionic kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  All the tests that need to fetch a git repo for testing failed with error 
message like: 
  CmdError: Command https://github.com/tytso/xfstests-bld> 
failed, rc=128, Command returned non-zero exit status
  * Command: 
  git clone https://github.com/tytso/xfstests-bld
  Exit status: 128
  Duration: 0.254368066788
   
  stderr:
  Cloning into 'xfstests-bld'...
  fatal: unable to access 'https://github.com/tytso/xfstests-bld/': 
gnutls_handshake() failed: An unexpected TLS packet was received.

  If you fetch this repo manually it will work (even with proxy configured)
  This needs to be investigated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Apr 10 11:35:24 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1762672] [NEW] TPM on Dell XPS 13 stopped working after upgrade to 18.04

2018-04-10 Thread Alexey Bazhin

Public bug reported:

 [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
 [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
 [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
 [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
 [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
 [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
 [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
 [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
 [3.423100] tpm tpm0: TPM self test failed
 [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

Discussion https://lkml.org/lkml/2017/12/6/284

Fix
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.15.0.13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  baz2268 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Apr 10 11:41:57 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=/dev/mapper/cryptswap1
InstallationDate: Installed on 2018-03-01 (39 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-13-generic N/A
 linux-backports-modules-4.15.0-13-generic  N/A
 linux-firmware 1.173
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.1
dmi.board.name: 02PG84
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd01/25/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  TPM on Dell XPS 13 stopped working after upgrade to 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
   [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest
   [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest
   [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest
   [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest
   [3.423100] tpm tpm0: TPM self test failed
   [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  Discussion https://lkml.org/lkml/2017/12/6/284

  Fix
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  baz2268 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 10 11:41:57 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2018-03-01 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=/dev/mapper/system-root ro quiet splash crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9

[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1758856

Title:
  retpoline hints: primary infrastructure and initial hints

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

Bug description:
  Tracking bug for the application of the retpoline hint tracking
  support.

  We are having terrible trouble with hints changing on every build.
  Upstream is moving to hinting those indirections which have been
  reviewed and are good.  This includes direct hinting of PVOPS and the
  like which are the ones which change all the time as new ones appear
  and dissappear.

  Backport the hint support and add our own bespoke checkers against
  this data.

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

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

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1723127

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [impact]

  The i40e driver sometimes causes a "malicious device" event that the
  firmware detects, which causes the firmware to reset the nic, causing
  an interruption in the network connection - which can cause further
  problems, e.g. if the interface is in a bond; the reset will at least
  cause a temporary interruption in network traffic.

  [fix]

  The upstream patch to fix this adjusts how the driver fragments TX
  data; the "malicious driver" detected by the firmware is a result of
  incorrectly crafted TX fragment descriptors (the firmware has specific
  complicated restrictions on this).  The patch is from Intel, and they
  suggested this specific patch to address the problem; additionally I
  have checked with someone who reported this to me and provided a test
  kernel with the patch to them, and they have been able to run ~6 weeks
  so far without reproducing the issue; previously they could reproduce
  it as quickly as a day, but usually within 2-3 weeks.

  [test case]

  the bug is unfortunately very difficult to reproduce, but as shown in
  this (and previous) bug comments, some users of the i40e have traffic
  that can consistently reproduce the problem (although usually on the
  order of days, or longer, to reproduce).  Reproducing is easily
  detected, as the nw traffic will be interrupted and the system logs
  will contain a message like:

  i40e :02:00.1: TX driver issue detected, PF reset issued

  [regression potential]

  the patch for this alters how tx is fragmented by the driver, so a
  possible regression would likely cause problems in TX traffic and/or
  additional "malicious device detection" events.


  [original description]

  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1723127

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [impact]

  The i40e driver sometimes causes a "malicious device" event that the
  firmware detects, which causes the firmware to reset the nic, causing
  an interruption in the network connection - which can cause further
  problems, e.g. if the interface is in a bond; the reset will at least
  cause a temporary interruption in network traffic.

  [fix]

  The upstream patch to fix this adjusts how the driver fragments TX
  data; the "malicious driver" detected by the firmware is a result of
  incorrectly crafted TX fragment descriptors (the firmware has specific
  complicated restrictions on this).  The patch is from Intel, and they
  suggested this specific patch to address the problem; additionally I
  have checked with someone who reported this to me and provided a test
  kernel with the patch to them, and they have been able to run ~6 weeks
  so far without reproducing the issue; previously they could reproduce
  it as quickly as a day, but usually within 2-3 weeks.

  [test case]

  the bug is unfortunately very difficult to reproduce, but as shown in
  this (and previous) bug comments, some users of the i40e have traffic
  that can consistently reproduce the problem (although usually on the
  order of days, or longer, to reproduce).  Reproducing is easily
  detected, as the nw traffic will be interrupted and the system logs
  will contain a message like:

  i40e :02:00.1: TX driver issue detected, PF reset issued

  [regression potential]

  the patch for this alters how tx is fragmented by the driver, so a
  possible regression would likely cause problems in TX traffic and/or
  additional "malicious device detection" events.


  [original description]

  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1758856

Title:
  retpoline hints: primary infrastructure and initial hints

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

Bug description:
  Tracking bug for the application of the retpoline hint tracking
  support.

  We are having terrible trouble with hints changing on every build.
  Upstream is moving to hinting those indirections which have been
  reviewed and are good.  This includes direct hinting of PVOPS and the
  like which are the ones which change all the time as new ones appear
  and dissappear.

  Backport the hint support and add our own bespoke checkers against
  this data.

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

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

[Kernel-packages] [Bug 1750349] Re: [Hyper-V] include kvp fix for Avoid reading past allocated blocks from KVP file

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1750349

Title:
  [Hyper-V] include kvp fix for Avoid reading past allocated blocks from
  KVP file

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  This commit is being requested in Bionic and linux-azure by Microsoft.  It 
has 
  already been applied to Bionic.  It is being requested in Artful, so it makes
  it's way into linux-azure through the re-base process.

  This fix is required if a large number of records are injected into a pool, 
  which can cause the kvp daemon to crash.

  This commit has been cc'd to upstream stable.  However, it has not yet been 
applied
  to Artful, since upstream 4.13 is EOL.

  == Fix ==
  297d6b6e56c2 ("hv: kvp: Avoid reading past allocated blocks from KVP file")

  == Regression Potential ==
  Low. This patch has also been sent to upstream stable, so it has had 
additional upstream
  review.

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

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

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

[Kernel-packages] [Bug 1739665] Re: [FFE][Feature] KVM CLX avx512_vnni

2018-04-10 Thread Stefan Bader

Due to time constraints and because we would deviate further and further
away from Debian, we are not planning to update the Xen version for
Bionic.

** Changed in: xen (Ubuntu Bionic)
   Status: Incomplete => 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/1739665

Title:
  [FFE][Feature] KVM CLX avx512_vnni

Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released
Status in xen package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in qemu source package in Bionic:
  Fix Released
Status in xen source package in Bionic:
  Won't Fix

Bug description:
  This feature has been released in ICX platform and the definition of 
AVX512_VNNI as below
   AVX512_VNNI Vector Nerual Network Instructions, an addition to AVX512. 
cpuid.(7,0). ECX[11]

  This is a new instruction to support machine learning. This
  instructions is pure HW features, currently, there is no test cases
  for this new instruction, we only check CPUID info by cpuid tool.

  Target Kernel: 4.16
  Target Qemu: 2.12
  Target Release: 18.04

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

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

[Kernel-packages] [Bug 1759188] Re: [8086:3e92] display becomes blank after S3

2018-04-10 Thread AceLan Kao

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

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  [   38.304449] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.304462] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK on first 
message, retry
  [   38.306726] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.306733] [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent 
adapter i915 gmbus dpd
  [   38.311251] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
HDMI ID: DP-HDMI ADAPTOR\004 (err 0)
  [   38.313538] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
adaptor ID: 44 (err 0)
  [   38.313554] [drm:intel_hdmi_set_edid [i915]] DP dual mode adaptor (type 1 
HDMI) detected (max TMDS clock: 165000 kHz)
  [   38.313557] [drm:drm_helper_hpd_irq_event [drm_kms_helper]] 
[CONNECTOR:115:HDMI-A-1] status updated from disconnected to disconnected

  [Fix]
  This commit pointed out by Timo fixes the issue.

  [Regression Potential]
  Should be low, although the change applies broadly.
  From the patch description, it explains it should be safe.
  > This workaround was designed to minimize the impact only
  > to save the bad case with that link rates. But HW engineers
  > indicated that it should be safe to apply broadly, although
  > they were expecting the DPLL0 link rate to be unchanged on
  > runtime.

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

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

[Kernel-packages] [Bug 1054458] Re: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'

2018-04-10 Thread Nafallo Bjälevik

This bug have popped up again in Bionic.

nafallo@wendigo:~$ nvidia-detector
Traceback (most recent call last):
  File "/usr/bin/nvidia-detector", line 8, in 
a = NvidiaDetection(printonly=True, verbose=False)
  File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 
68, in __init__
self.getData()
  File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 
151, in getData
driver_version = self.__get_value_from_name(stripped_package_name)
  File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 
87, in __get_value_from_name
v = int(name)
ValueError: invalid literal for int() with base 10: 'driver-390'

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

Title:
  nvidia-detector crashed with ValueError in __get_value_from_name():
  invalid literal for int() with base 10: 'experimental-304'

Status in nvidia-common package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-common source package in Precise:
  Fix Released
Status in ubuntu-drivers-common source package in Precise:
  Invalid
Status in nvidia-common source package in Quantal:
  Invalid
Status in ubuntu-drivers-common source package in Quantal:
  Fix Released

Bug description:
  If other people report this at the current level with xorg/nvidia it
  might be a bug. It is also possible the error stems from a bad
  combination of free and proprietary material. Further details will be
  provided as necessary/available.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: ubuntu-drivers-common 1:0.2.69
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  Date: Fri Sep 21 22:48:18 2012
  ExecutablePath: /usr/bin/nvidia-detector
  InterpreterPath: /usr/bin/python3.2mu
  ProcCmdline: /usr/bin/python3.2 /usr/bin/nvidia-detector
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   LANGUAGE=de_CH:de
  PythonArgs: ['/usr/bin/nvidia-detector']
  SourcePackage: ubuntu-drivers-common
  Title: nvidia-detector crashed with ValueError in __get_value_from_name(): 
invalid literal for int() with base 10: 'experimental-304'
  UpgradeStatus: Upgraded to quantal on 2012-07-31 (52 days ago)
  UserGroups: audio pulse pulse-access video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1054458/+subscriptions

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

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

--- Comment From indira.pr...@in.ibm.com 2018-04-10 07:24 EDT---
Hi Jose,

Is this fix available in official ubutnu1804 build

Regards,
Indira

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

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Problem Description:
  ===
  Performed HOTPLUG cpu attach operation for the guest and guest console 
becomes unresponsive.

  Steps to re-create:
  ==
  1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels
   
  2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.15.0-12-generic

  root@boslcp3g3:/kte/tools/setup.d# uname -a
  Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g3:/kte/tools/setup.d# uname -r
  4.15.0-12-generic

  3. Started HTX & stress-ng for on guest for 10-15 min

  4. Cleaned up the tests to perform hot-plug and ensure enough memory
  and cpu was there (killed all Process using kill)

  5. Performed cpu hot-plug and guest went into hung state

  Before Hotplug:

  root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu
64

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  



  root@boslcp3:~#  

  6. After this operation, guest becomes unrepsonsive as below

  
  root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more 
than 120 seconds.
  [ 3626.146375]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3626.146699]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 
seconds.
  [ 3626.147016]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 
seconds.
  [ 3626.147361]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds.
  [ 3626.147686]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds.
  [ 3626.147937]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds.
  [ 3626.148173]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds.
  [ 3626.148406]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  root@boslcp3g3:~#
  root@boslcp3g3:~# ps -ef | grep stress-ng
  [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds.
  [ 3746.978221]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3746.978534]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4446.361899] systemd[1]: Failed to start Journal Service.
  [ 4897.632142] systemd[1]: Failed to start Journal Service.


  ^Z
  ^X
  ^C
  ^Z
  ^X
  ^C

  7.

[Kernel-packages] [Bug 1759961] Re: Update to 5.49 in Bionic (mostly bug-fix release)

2018-04-10 Thread Sebastien Bacher

The update has some new features and it's a bit late in the cycle now,
that sounds rather SRU material at this point ... Daniel, Konrad, what
do you think?

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

Title:
  Update to 5.49 in Bionic (mostly bug-fix release)

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

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

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

[Kernel-packages] [Bug 1762652] 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 1762652

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

Title:
  perf DWARF unwind failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10. To reproduce:

  $ perf test
  [...]
  57: DWARF unwind   : FAILED!
  [...]

  It seems perf is somehow mis-configured.

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1759920

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank 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/1759920

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1759511

Title:
  Fix an issue that when system in S3, USB keyboard can't wake up the
  system.

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# 
wakeup event, so USB device can't wake the system.

  [Test]
  Intel NUC can't be waken up by USB keyboard when the system is in S3.
  With the patch, USB keyboard can wake up the system.

  [Regression Potential]
  Low.
  The issue starts appearing from Gemini Lake, older generation hardware 
shouldn't get affected.

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

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

[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-xenial

** Tags added: verification-needed-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/1760876

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed

Bug description:
  Was installing the kernel 4.15.0-14-generic when that crash happened.
  Now libelf-dev is requested and need to be added as a dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 15:39:06 2018
  PackageVersion: 18.03.00-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fwts
  Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1761456] Re: linux: 4.13.0-39.44 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
+ bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

Title:
  linux: 4.13.0-39.44 -proposed tracker

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

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

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

  backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761456/+subscriptions

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

[Kernel-packages] [Bug 1759188] Re: [8086:3e92] display becomes blank after S3

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1759188

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  [   38.304449] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.304462] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK on first 
message, retry
  [   38.306726] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.306733] [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent 
adapter i915 gmbus dpd
  [   38.311251] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
HDMI ID: DP-HDMI ADAPTOR\004 (err 0)
  [   38.313538] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
adaptor ID: 44 (err 0)
  [   38.313554] [drm:intel_hdmi_set_edid [i915]] DP dual mode adaptor (type 1 
HDMI) detected (max TMDS clock: 165000 kHz)
  [   38.313557] [drm:drm_helper_hpd_irq_event [drm_kms_helper]] 
[CONNECTOR:115:HDMI-A-1] status updated from disconnected to disconnected

  [Fix]
  This commit pointed out by Timo fixes the issue.

  [Regression Potential]
  Should be low, although the change applies broadly.
  From the patch description, it explains it should be safe.
  > This workaround was designed to minimize the impact only
  > to save the bad case with that link rates. But HW engineers
  > indicated that it should be safe to apply broadly, although
  > they were expecting the DPLL0 link rate to be unchanged on
  > runtime.

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

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

[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1734327

Title:
  Kernel panic on a nfsroot system

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

Bug description:
  == SRU Justification ==
  The following commit introduced a regression identified in bug 1734327:
  ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of 
the remaining blobs")

  The regression causes a kernel panic to occur after multiple TCP connection 
  creations/closures to the localhost.  The bug was found using STAF RPC calls, 
  but is easily reproducible with SSH.

  A revert of commit ac8f82a0b6d9 is needed to resolve this bug.  However, 
commit 4ae2508f0bed
  also needs to be reverted because it depend on commit ac8f82a0b6d9.

  == Fix ==
  Revert 4ae2508f0bed ("UBUNTU: SAUCE: LSM stacking: add stacking support to 
apparmor network hooks")
  Revert ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure 
management of the remaining blobs")

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



  
  == Original Bug Description ==
  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.

  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw

  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64

  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash

  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:

[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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

** Tags added: verification-needed-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/1759312

Title:
AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu
17.10

Bug description:

== SRU Justification ==
AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal
machines
causing trouble to userspace tools and software that rely on that
information,
notably operf and opreport (from oprofile 1.2.0+) will refuse to run without
that information.

This bug is fixed by commit e4b79900222b, which is in linux-next and just
landed in mainline, but is not contained in any release as of yet.

== Fix ==
e4b79900222b ("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU
features")

== Regression Potential ==
Low. Limited to powerpc.

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

---Problem Description---
AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10

---Additional Hardware Info---
Architecture:ppc64le
Byte Order: Little Endian
CPU(s): 176
On-line CPU(s) list: 0-175
Thread(s) per core: 4
Core(s) per socket: 22
Socket(s): 2
NUMA node(s):8
Model: 2.2 (pvr 004e 1202)
Model name: POWER9, altivec supported
CPU max MHz: 2800.
CPU min MHz: 2300.
L1d cache: 32K
L1i cache: 32K
L2 cache:512K
L3 cache:10240K
NUMA node0 CPU(s): 0-87
NUMA node8 CPU(s): 88-175
NUMA node250 CPU(s):
NUMA node251 CPU(s):
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):

Machine Type = P9, DD2.2, Witherspoon, baremetal

---Steps to Reproduce---
AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal
machines causing trouble to userspace tools and software that relie on that
information, notably operf and opreport (from oprofile 1.2.0+) will refuse to
run without that information show a error message like:

gromero@ltc-wspoon3:/boot$ operf
NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM
AT_PLATFORM: power9; AT_BASE_PLATFORM: (null)
Unable to obtain cpu_type
Verify that a pre-1.0 version of OProfile is not in use.
If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile
installation, and use its 'opcontrol' command, passing the --deinit option.
Unable to ascertain cpu type. Exiting.

---uname output---
linux-image-4.13.0-36-generic 4.13.0-36.40

Userspace tool common name: operf, opreport

Dear maintainer. please consider applying the following fix that's
already available upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f

Thank you.

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

[Kernel-packages] [Bug 1759088] Re: can't record sound via front headset port on the Dell Precision 3630

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1759088

Title:
  can't record sound via front headset port on the Dell Precision 3630

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]
  The Dell Precision 3630 is a desktop computer, it has only one front headset
  jack on it, after we plug a headset in it, we can't record sound via the
  headset-mic.

  And Realtek told us that "This platform was the fixed type headset only for
  iphone type. Fixed type headset was not run for default headset mode rule.
  It's hardware fixed type solution. Don't need to run software headset mode.
  Hardware layout not support UAJ functions."

  And Realtek submitted this patch to fix this problem.

  [Fix]
  With this patch, the driver only set pin 0x19 as the headset-mic and will not
  call alcxxx_headset_mode init function anymore since the circuit is hardware
  fixed to be iphone-type headset-mic.

  [Test Case]
  Boot up the system, and plug a iphone-type headset, record the sound via
  headset-mic, it can record the sound and sound quality is pretty good.

  [Regression Potential]
  Very low, this patch is only specific to precision 3930 (subsystem id:
  0x10280871 and 0x10280872).

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

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

[Kernel-packages] [Bug 1758829] Re: speaker can't output sound anymore after system resumes from S3 on a lenovo machine with alc257

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1758829

Title:
  speaker can't output sound anymore after system resumes from S3 on a
  lenovo machine with alc257

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]
  After booting up, the speaker works well. If we suspend the machine then 
resume
  it back, the speaker can't output sound, even rebooting can't make the speaker
  work, we need to power off the machine then power up the machine, the speaker
  can work again.

  [Fix]
  We need to add the basic support for the codec alc257 first (0001-xxx.patch),
  then add hooking function for this codec and clear the bit of 15 for register
  0x57 (0002-xxx.patch). Both of these two patches come from mainline kernel.

  [Test Case]
  After booting up the system, suspend the machine, then resume the machine,
  test the speaker, the speaker can output sound. Repeat the testing steps many
  times, the speaker still can work.

  [Regression Potential]
  Very low, since the 1st patch just add the support for a new codec alc257, it
  will not affect other codecs. The 2nd patch just apply a fix for alc257, it
  doesn't affect other codecs too. And both of them come from mainline and
  realtek.

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

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

[Kernel-packages] [Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1757584

Title:
  Let headset-mode initialization be called on Dell Precision 3930

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.

  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.

  [Test Case]
  plug the headset and play or record the sound on this machine, both playing
  and recording work well.

  [Fix]
  one commit from mainline kernel.

  [Regression Potential]
  very low, since this patch only applies to the specific Dell machine 
Precision 3930.

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

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

[Kernel-packages] [Bug 1755073] Re: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1755073

Title:
  ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64

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

Bug description:
  == SRU Justification ==

  Enabling virtual mapped kernel stacks breaks the thunderx_zip driver.
  On compression or decompression the executing CPU hangs in an endless
  loop. The reason for this is the usage of __pa() by the driver that
  does not work for an address that is not part of the 1:1 mapping.

  == Fix ==

  The patch in comment #12 fixes it.
  To reproduce the bug (and test the new kernel), see comment #9.

  == Regression Potential ==

  The patch affects only the thunderx_zip driver (that is already in a
  completely broken state), so the regression potential is low.

  ---

  This is a POTENTIAL REGRESSION.

  This test has passed with 4.13.0-36.40, but not 4.13.0-37.42

  The test will stuck with error message in dmesg:
  ubuntu@starmie-kernel:~$ dmesg
  [  470.227210] zram: Added device: zram0
  [  472.262544] zram0: detected capacity change from 0 to 134217728
  [  472.396960] EXT4-fs (zram0): mounted filesystem with ordered data mode. 
Opts: (null)
  [  475.761947] zram0: detected capacity change from 134217728 to 0
  [  476.796641] zram0: detected capacity change from 0 to 134217728
  [  476.909118] EXT4-fs (zram0): mounted filesystem with ordered data mode. 
Opts: (null)
  [  480.233817] zram0: detected capacity change from 134217728 to 0
  [  481.239001] zram0: detected capacity change from 0 to 134217728
  [  508.079684] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! 
[mkfs.ext4:2253]
  [  508.086994] Modules linked in: lz4 lz4_compress zram nls_iso8859_1 
thunderx_edac i2c_thunderx thunderx_zip i2c_smbus shpchp cavium_rng_vf 
cavium_rng gpio_keys ipmi_ssif uio_pdrv_genirq uio ipmi_devintf ipmi_msghandler 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt aes_ce_cipher 
fb_sys_fops crc32_ce crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci 
thunder_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd
  [  508.087138] CPU: 8 PID: 2253 Comm: mkfs.ext4 Not tainted 4.13.0-37-generic 
#42-Ubuntu
  [  508.087141] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [  508.087144] task: 801f57a86900 task.stack: 23ec
  [  508.087158] PC is at zip_deflate+0x184/0x2e8 [thunderx_zip]
  [  508.087164] LR is at zip_deflate+0x17c/0x2e8 [thunderx_zip]
  [  508.087167] pc : [] lr : [] pstate: 
20400145
  [  508.087169] sp : 23ec3580
  [  508.087171] x29: 23ec3580 x28: 
  [  508.087177] x27: 801f57a86900 x26: 0001b104
  [  508.087182] x25: 801f5618c000 x24: 801f6a15bc18
  [  508.087188] x23: 1000 x22: 23ec3688
  [  508.087193] x21: 801f5a2d4880 x20: 801f6a15bc18
  [  508.087199] x19: 23ec3608 x18: 
  [  508.087204] x17: 0001 x16: 
  [  508.087209] x15: bd4048db x14: fa13
  [  508.087215] x13: 1000 x12: fa12
  [  508.087220] x11:  x10: 
  [  508.087225] x9 :  x8 : 
  [  508.087230] x7 :  x6 : 8000101d6080
  [  508.087236] x5 : 01a69058 x4 : 0008
  [  508.087241] x3 :  x2 : 
  [  508.087246] x1 : 801f6a15be08 x0 : 
  [  508.087252] Call trace:
  [  508.087256] Exception stack(0x23ec3440 to 0x23ec3580)
  [  508.087260] 3440:  801f6a15be08  

  [  508.087264] 3460: 0008 01a69058 8000101d6080 

  [  508.087268] 3480:

[Kernel-packages] [Bug 1758800] Re: hda driver initialization takes too much time on the machine with coffeelake audio controller [8086:a348]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1758800

Title:
  hda driver initialization takes too much time on the machine with
  coffeelake audio controller [8086:a348]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]

  We have a couple of laptop and desktop computers, all of them are cfl 
platforms
  and all of them have cfl audio controller [8086:a348], and these computers 
have
  different realtek codecs on them (alc256, alc255, alc289 and ...). The hda
  driver takes too much time (3 secs - 8 secs) to initialize on these machines.
  This problem never happened on kbl, skl, bdw, ... before.

  Sometimes this can make pulseaudio can't work well.

  pulseaudio starts, but the driver (as kernel modules) initialization has not
  finished, then there is no valid sink in the pulseaudio. At this moment, some 
UI
  Apps already start using pulseaudio to play sound, but users can't hear the 
sound
  as expected. This problem never happened before, it is exposed on cfl 
platforms,
  and all cfl platforms (with audio controller 8086:a348) have this problem.

  [Fix]
  Set the polling mode can fix this problem, and this workaround is in the
  mainline kernel.

  [Test Case]
  Boot the machine and check the dmesg, from the hda log, we can see the driver
  initialization is finished within 0.1s and pulseaudio works well.

  [Regression Potential]
  No regression, this fix is only for CFL audio controller (8086:a348), and
  in theory, polling mode is safe for all audio controllers, using interrupt
  mode rather than polling mode on other platforms just wants to save polling
  overhead for CPUs, since interrupt mode can't work well on CFL platform, we
  have to use polling mode.

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

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

[Kernel-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

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


** Tags added: verification-needed-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/1757565

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Fix Committed
Status in tar source package in Artful:
  New

Bug description:
  
  == SRU Justification ==
  This bug causes btrfs and tar sparse to truncate archives.  This bug has been 
  fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of 
f48bf66b662e.

  These commits were cc'd to upstream stable and are already in Bionic.  
However, upstream
  4.13 is EOL, so Artful never recieved the fixes, which is the reason for
  the SRU request.

  == Fixes ==
  f48bf66b662e ("Btrfs: move definition of the function 
btrfs_find_new_delalloc_bytes")
  e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered 
append writes")

  == Regression Potential ==
  Low.  This fix was also sent and accepted to stable, so it has had additional 
upstream review.

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



  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 4.13.0.37.40
    Candidate: 4.13.0.37.40
    Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/
  https://www.spinics.net/lists/linux-btrfs/msg56768.html
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcEnviron:

[Kernel-packages] [Bug 1591167] Re: Bluetooth: hci0 link tx timeout with Intel Corporation Wireless 7260

2018-04-10 Thread michele orlandi

Hope this helps, I think I found a workaround for my bluetooth tethering
issue with Android.

NOTE: This assumes that you're using tlp power manager.

Find your bluetooth device like so:

tlp-usblist | grep btusb

Bus 002 Device 011 ID : control = on,   autosuspend_delay_ms =
2000 -- Intel Corp.  (btusb)


add your device to your /etc/default/tlp:
USB_BLACKLIST=:

restart tlp in order to load your changes:
sudo service tlp restart

When I received a call the BT device timed out again, but not every 5
minutes like before.

I'll keep testing this and will let you know if confirmed.

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

Title:
  Bluetooth: hci0 link tx timeout with Intel Corporation Wireless 7260

Status in linux-firmware package in Ubuntu:
  Fix Committed

Bug description:
  reported upstream as well :
  https://bugzilla.kernel.org/show_bug.cgi?id=120161

  Starting with Ubuntu 16.04 (no problem in 15.10) the bluetoth stack
  crashes several times a day:

  May 20 11:54:59 thinktank kernel: [ 6274.939039] Bluetooth: hci0 link tx 
timeout
  May 20 11:54:59 thinktank kernel: [ 6274.939046] Bluetooth: hci0 killing 
stalled connection 7c:6d:62:f1:ef:b1
  May 20 11:55:01 thinktank kernel: [ 6276.942116] Bluetooth: hci0 command 
0x041f tx timeout
  May 20 11:55:03 thinktank kernel: [ 6278.946094] Bluetooth: hci0 command 
0x0406 tx timeout

  I have an Apple Keyboard and Apple Magicmouse connected and the entire
  stack is down after seeing the above crash. These are the devices:

  input: Apple Wireless Keyboard as 
/devices/pci:00/:00:14.0/usb2/2-11/2-11:1.0/bluetooth/hci0/hci0:512/0005:05AC:023A.0002/input/input18
  apple 0005:05AC:023A.0002: input,hidraw1: BLUETOOTH HID v0.50 Keyboard [Apple 
Wireless Keyboard] on 5c:c5:d4:5d:94:7b

  input: ... mouse as /devices/pci:00/:00:14.0/usb2/2-11/2-11:
  1.0/bluetooth/hci0/hci0:256/0005:05AC:030D.0001/input/input17
  magicmouse 0005:05AC:030D.0001: input,hidraw0: BLUETOOTH HID v0.84 Mouse [... 
mouse] on 5c:c5:d4:5d:94:7b

  No input or re-pairing is possible after those timeout messages.
  Reloading the kernel firmware modules doesn't help either:

  modprobe -r btusb
  modprobe btusb

  The only way to bring the bluetooth stack up again is to toggle to
  standby (S3) and wake up the system again. In this case there firmware
  is reloaded and everything back to life:

  May 20 10:10:35 thinktank kernel: [   10.017143] Bluetooth: hci0: read Intel 
version: 370710018002030d00
  May 20 10:10:35 thinktank kernel: [   10.019069] Bluetooth: hci0: Intel 
Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  May 20 10:10:35 thinktank kernel: [   10.160231] Bluetooth: hci0: Intel 
Bluetooth firmware patch completed and activated
  May 20 10:10:35 thinktank systemd[1]: Starting Bluetooth service...
  May 20 10:10:36 thinktank bluetoothd[1147]: Bluetooth daemon 5.37
  May 20 10:10:36 thinktank systemd[1]: Reached target Bluetooth.

  May 20 10:10:36 thinktank kernel: [   11.412940] Bluetooth: BNEP (Ethernet 
Emulation) ver 1.3
  May 20 10:10:36 thinktank kernel: [   11.412943] Bluetooth: BNEP filters: 
protocol multicast
  May 20 10:10:36 thinktank kernel: [   11.412948] Bluetooth: BNEP socket layer 
initialized
  May 20 10:10:36 thinktank bluetoothd[1147]: Bluetooth management interface 
1.10 initialized

  Since the problem did not occur with Ubuntu 15.10 I traced the issue down to 
the changed firmware files:
  /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  of package linux-firmware

  Bad:
  $ sha1sum ibt-hw-37.7.10-fw-1.80.2.3.d.bseq.ubuntu
  b697de26b72804af9d9385d13e989a72fd364d75  ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  Filesize : 25631

  origin:
  2016-02-03linux-firmware: Update firmware patch for Intel Bluetooth 7260 
(B3/B4)
  
http://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git/commit/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq?id=7b1a5cb6a2cd379f470058580be2a41f5d5c4867

  Good (included in Ubuntu 15.10):

  $ sha1sum ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  19f01d6469f30a9b1d7c214615ea39ac5e9d875c  ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  Filesize : 25117

  origin:
  2015-09-24linux-firmware: Update firmware patch for Intel Bluetooth 7260 
(B3/B4)
  
http://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git/commit/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq?id=01f57c63a0d2fd822462b5eedb09ff3a92fbcb29

  The numbers in the file name do not correspond to version numbers:
  Therefore sha1sum and filesize given to distinguish.

  According to
  http://linuxwireless.org/en/users/Drivers/iwlwifi/#Bugzilla
  I may file a bug upstream.

  kernel: 4.4.0-22-generic

  Bluetooth Device:
  $ lsusb -d 8087:07dc
  Bus 002 Device 004: ID 8087:07dc Intel Corp.

  $ lspci -v
  03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
  Subsystem: Intel

[Kernel-packages] [Bug 1762709] Re: Unable to fetch git repos using autotest framework with Bionic kernel

This can be reproduced with the following python code on Bionic, with
the autotest framework cloned:

git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
sudo apt-get install -y python-minimal
python
from autotest.clientimport test, utils
import os

proxysets = [{'addr': 'squid.internal', 'desc': 'Running in the Canonical CI 
environment'},
  {'addr': '91.189.89.216', 'desc': 'Running in the Canonical 
enablement environment'},
  {'addr': '10.245.64.1', 'desc': 'Running in the Canonical 
enablement environment'}]
for proxy in proxysets:
cmd = 'nc -w 2 ' + proxy['addr'] + ' 3128'
try:
utils.system_output(cmd, retain_output=False)
print proxy['desc']
os.environ['http_proxy'] = 'http://' + proxy['addr'] + ':3128'
os.environ['https_proxy'] = 'https://' + proxy['addr'] + ':3128'
break
except:
pass

utils.system('git clone https://github.com/tytso/xfstests-bld')


But it works without the proxy setting in the python code above.
I will file a RT for 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/1762709

Title:
  Unable to fetch git repos using autotest framework with Bionic kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  All the tests that need to fetch a git repo for testing failed with error 
message like: 
  CmdError: Command https://github.com/tytso/xfstests-bld> 
failed, rc=128, Command returned non-zero exit status
  * Command: 
  git clone https://github.com/tytso/xfstests-bld
  Exit status: 128
  Duration: 0.254368066788
   
  stderr:
  Cloning into 'xfstests-bld'...
  fatal: unable to access 'https://github.com/tytso/xfstests-bld/': 
gnutls_handshake() failed: An unexpected TLS packet was received.

  If you fetch this repo manually it will work (even with proxy configured)
  This needs to be investigated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Apr 10 11:35:24 2018
  HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

2018-04-10 Thread aljosa

Hello Clément, can you please inform developers about your finding:
https://www.spinics.net/lists/linux-input/msg51188.html

I've tried in Solus to execute the suggested commands, but have a
problem with permissions - any idea?

me@user ~ $ cd /sys/bus/hid/drivers/hid-multitouch
me@user /sys/bus/hid/drivers/hid-multitouch $ ls
0018:04F3:3043.0007  bind  module  new_id  uevent  unbind
me@user /sys/bus/hid/drivers/hid-multitouch $ echo "0018:04F3:3043.0007" > 
unbind
bash: unbind: Permission denied
me@user /sys/bus/hid/drivers/hid-multitouch $ echo 0018 04F3 3043 0013 > new_id
bash: new_id: Permission denied

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [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)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4
  U: Uniq=
  H:

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1761557/+attachment/5109278/+files/Lspci.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1761557/+attachment/5109276/+files/CurrentDmesg.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1761557] Re: Qualcom QCA6174 - regdomain: 0x5f

apport information

** Tags added: apport-collected bionic

** Description changed:

  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.
  
  Best regards
  Yu Kei
+ --- 
+ ApportVersion: 2.20.9-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ulrich 1242 F pulseaudio
+ CurrentDesktop: KDE
+ Dependencies:
+  
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
+ InstallationDate: Installed on 2018-04-01 (9 days ago)
+ InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
+ MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
+ Package: linux-firmware 1.173
+ PackageArchitecture: all
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-13-generic N/A
+  linux-backports-modules-4.15.0-13-generic  N/A
+  linux-firmware 1.173
+ Tags:  bionic
+ Uname: Linux 4.15.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/13/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P01HAD.005.170613.WY.1108
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: SM-W620NZKBDBT
+ dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 32
+ dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
+ dmi.product.family: SAMSUNG GALAXY
+ dmi.product.name: Galaxy Book 10.6
+ dmi.product.version: P01HAD
+ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1761557/+attachment/5109274/+files/AlsaInfo.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1761557/+attachment/5109275/+files/CRDA.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

2018-04-10 Thread Frank Heimes

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Changed in: ubuntu-z-systems
   Importance: Undecided => Critical

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

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

[Kernel-packages] [Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

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

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

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

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1761557/+attachment/5109277/+files/IwConfig.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1762652] Re: perf DWARF unwind failed

2018-04-10 Thread Zeno

apport-collect crashes here, sorry. I'm using a German locale and KDE.
Error:

  File "/usr/share/apport/apport-kde", line 359, in ui_update_view
QTreeWidgetItem(keyitem, [str(line)])
UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 
87: ordinal not in range(128)


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

Title:
  perf DWARF unwind failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10. To reproduce:

  $ perf test
  [...]
  57: DWARF unwind   : FAILED!
  [...]

  It seems perf is somehow mis-configured.

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

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

[Kernel-packages] [Bug 1758797] Re: [Ubuntu 18.04] USB Type-C test failed on GLK

2018-04-10 Thread Thadeu Lima de Souza Cascardo

The module already has an alias that should allow it to autoload:

alias:  acpi*:PNP0CA0:*

What is the output of ls /sys/bus/acpi/devices/*PNP0CA0* on such a system?
Or grep -H . /sys/bus/acpi/devices/*PNP0CA0*/modalias?

Cascardo.

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

Title:
  [Ubuntu 18.04] USB Type-C test failed on GLK

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  Platform information:
  Label: GLK02SDP
  Processor: Silver N5000
  Bios: GELKRVPA.X64.0083.B30.1801162142
  OS: Ubuntu 18.04
  Kernel: 4.15.0-10-generic

  Details:
  Bios: system setup -> system component -> USB Type-C 

  root@GLK02:~# cat /boot/config-4.15.0-10-generic | grep -i ucsi
  CONFIG_TYPEC_UCSI=m
  CONFIG_UCSI_ACPI=m

  root@GLK02:~# ls /sys/class/typec/
  root@GLK02:~#

  USB Type-C ports could not be seen.

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

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1761557/+attachment/5109280/+files/ProcCpuinfoMinimal.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

apport information

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

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-10 Thread pdf

Tested kernel from xenial-proposed on an affected system, and the issue
there appears to be resolved.

$ uname -r
4.4.0-120-generic

$ apt policy linux-image-generic
linux-image-generic:
  Installed: 4.4.0.120.126
  Candidate: 4.4.0.120.126
  Version table:
 *** 4.4.0.120.126 400
400 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.4.0.119.125 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial-security/main amd64 Packages
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial-updates/main amd64 Packages
 4.4.0.21.22 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main amd64 
Packages

$ apt policy intel-microcode
intel-microcode:
  Installed: 3.20180312.0~ubuntu16.04.1
  Candidate: 3.20180312.0~ubuntu16.04.1
  Version table:
 *** 3.20180312.0~ubuntu16.04.1 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial-security/main amd64 Packages
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.20151106.1 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/restricted 
amd64 Packages


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

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

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

apport information

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

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

Cherry picked the auto-detection patches into bionic, set
CONFIG_EXPOLINE_AUTO=y and CONFIG_KERNEL_NOBP=n.

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

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

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk

2018-04-10 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Triaged => Fix Committed

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

Title:
  [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on  failed'
  when setting up a second end-to-end encrypted disk

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Problem Description:
  Environment: z14 VM Guest system with one CEX6C CCA coprocessor
  in toleration mode (i.e. CEX6 HW presented as CEX5)
  OS: Ubuntu 18.04 Prerelease
  Setting up a second dm-crypt device using protected CCA paes-xts keys fails.
  The problem is reproducible.

  Details
  ===
  Setting up two or more plain end-to-end encrypted disks using 'cryptsetup'
  fails when using a cipher based on the protected key mechanism.
  The setup needs the paes and pkey modules loaded, the former providing the
  paes-xts-plain64 cipher (cat /proc/crpyto |grep paes).

  A second attempt to establish an end-to-end encrypted disk fails
  with : "device-mapper: reload ioctl on failed: No such file or directory."

  The problem is independent of the second encrypted disk being based on
  a second DASD or second partition on one DASD.

  ---uname output---
  Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
  1.) The following cryptsetup statement works, and is the first one I issued.
  cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher 
paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1
  2.) After this successful statement, I issued the following:
  cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher 
paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2
  device-mapper: reload ioctl on failed: No such file or directory.

  See attached patch (comment #1) as fix.

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

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

[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk

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

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

Title:
  [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on  failed'
  when setting up a second end-to-end encrypted disk

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Problem Description:
  Environment: z14 VM Guest system with one CEX6C CCA coprocessor
  in toleration mode (i.e. CEX6 HW presented as CEX5)
  OS: Ubuntu 18.04 Prerelease
  Setting up a second dm-crypt device using protected CCA paes-xts keys fails.
  The problem is reproducible.

  Details
  ===
  Setting up two or more plain end-to-end encrypted disks using 'cryptsetup'
  fails when using a cipher based on the protected key mechanism.
  The setup needs the paes and pkey modules loaded, the former providing the
  paes-xts-plain64 cipher (cat /proc/crpyto |grep paes).

  A second attempt to establish an end-to-end encrypted disk fails
  with : "device-mapper: reload ioctl on failed: No such file or directory."

  The problem is independent of the second encrypted disk being based on
  a second DASD or second partition on one DASD.

  ---uname output---
  Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
  1.) The following cryptsetup statement works, and is the first one I issued.
  cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher 
paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1
  2.) After this successful statement, I issued the following:
  cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher 
paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2
  device-mapper: reload ioctl on failed: No such file or directory.

  See attached patch (comment #1) as fix.

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

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

[Kernel-packages] [Bug 1758471] Re: apparmor: fix bad __initdata tagging on, apparmor_initialized

2018-04-10 Thread John Johansen

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

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

Title:
  apparmor: fix bad __initdata tagging on, apparmor_initialized

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

Bug description:
  When building the Xenial kernel we get the following warning

  WARNING: vmlinux.o(.text+0x393a60): Section mismatch in reference from
  the function param_set_aauint() to the variable
  .init.data:apparmor_initialized

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

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

[Kernel-packages] [Bug 1729128] Re: Raspberry Pi 3 microSD support missing from the installer

2018-04-10 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Raspberry Pi 3 microSD support missing from the installer

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

Bug description:
  [Impact]

  Without this module in block-modules.udeb, the default generic arm64
  image cannot install on a raspberrypi3 board.

  [Test case]

  Build the block-modules.udeb with and without the attached patch and
  check for the presence of the drivers/mmc/host/bcm2835.ko.

  [Regression Potential]

  None, we are adding a ko to a udeb, not removing it.

  ---

  
  Please add bcm2835 to block-modules on arm64 (and armhf?).

  artful's arm64 d-i mini.iso works fine on Raspberry Pi 3 when booting
  with a UEFI-capable u-boot, except for one detail: mmc/host/bcm2835.ko
  is missing from block-modules, so you can't install to microSD without
  manually grabbing and loading the module.

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

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

[Kernel-packages] [Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

2018-04-10 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

[Kernel-packages] [Bug 1762603] Re: bluetooth keeps turning off

2018-04-10 Thread Aurélien PIERRE

Yes it looks like the same bug (at least for the GUI part), and it's a
Thinkpad as well.

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

Title:
  bluetooth keeps turning off

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Kernel-packages] [Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command

2018-04-10 Thread LGB [Gábor Lénárt]

[22596.884250] sysrq: SysRq : This sysrq operation is disabled.

I got this, if I try to trigger those sysreq events by echoing t/m into
that procfs file. I'm anyway curious how sysreq stuffs can be
enabled/disabled, since I seldom use ALT-SYSREQ- combos as well, and
many of them just reports the same as with this procfs trigger:
operation is disabled.

One thing though:

If I attach the thumb drive, everything is fine, lsblk shows it, etc, I
can remove it, lsblk does not show it, no problem. The problem seems to
have after the first event when I try to write onto the device, then
whatever I try even remove thumb drive physically, lsblk still shows it,
all the "sync" commands (and anything which tries to write onto) stuck
and cannot be killed. So even shutdown of system is problematic at this
point. Now I've tried fdisk (btw, no partition on the thumb drive). Just
displaying, everything is OK. However after the "w" command the problems
begins. By checking the /proc entry for the PID of the fdisk, I see:

# cat /proc/11283/status 
Name:   fdisk
Umask:  0022
State:  D (disk sleep)
[...]


# cat /proc/11283/stat
11283 (fdisk) D 11084 11283 10324 34827 11283 4194560 673 0 4 0 0 1 0 0 20 0 1 
0 2254524 21024768 877 18446744073709551615 94293651558400 94293651671008 
140732927217664 0 0 0 0 0 0 1 0 0 17 1 0 0 16 0 0 94293653771504 94293653778500 
94293676326912 140732927223610 140732927223625 140732927223625 140732927225836 0

Full output of status file:

# cat /proc/11283/status 
Name:   fdisk
Umask:  0022
State:  D (disk sleep)
Tgid:   11283
Ngid:   0
Pid:11283
PPid:   11084
TracerPid:  0
Uid:0   0   0   0
Gid:0   0   0   0
FDSize: 256
Groups: 0 
NStgid: 11283
NSpid:  11283
NSpgid: 11283
NSsid:  10324
VmPeak:21568 kB
VmSize:20532 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM:  4176 kB
VmRSS:  3508 kB
RssAnon: 372 kB
RssFile:3136 kB
RssShmem:  0 kB
VmData:  284 kB
VmStk:   132 kB
VmExe:   112 kB
VmLib:  3144 kB
VmPTE:80 kB
VmSwap:0 kB
HugetlbPages:  0 kB
CoreDumping:0
Threads:1
SigQ:   0/13289
SigPnd: 
ShdPnd: 
SigBlk: 
SigIgn: 
SigCgt: 
CapInh: 
CapPrm: 003f
CapEff: 003f
CapBnd: 003f
CapAmb: 
NoNewPrivs: 0
Seccomp:0
Cpus_allowed:   f
Cpus_allowed_list:  0-3
Mems_allowed:   
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0001
Mems_allowed_list:  0
voluntary_ctxt_switches:73
nonvoluntary_ctxt_switches: 0

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

Title:
  [18.04] writing on thumb drives causes hang for write op, shutdown and
  'sync' command

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded to 18.04. Since then, it's impossible to use thumb-
  drives. If I try, on the first write operation, that operation hangs.
  Trying to issue a 'sync' command that hangs too. After a while (some
  minutes or so?) I see the following in kernel log / dmesg (see later).
  It's not even possible to cleanly shut the computer down, as it also
  hangs then.

  kernel is:

  4.15.0-15-generic
  Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -S /boot/vmlinuz-4.15.0-15-generic 
  linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic
  $ dpkg -l linux-image-4.15.0-15-generic
  ii  linux-image-4.15.0-15-generic4.15.0-15.16  amd64  
   Linux kernel image for version 4.15.0 on 64 bit x86 SMP

  dmesg:

  
  [  110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd
  [  111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00
  [  111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  111.083441] usb 6-1: Product: DataTraveler 2.0
  [  111.083444] usb 6-1: Manufacturer: Kingston
  [  111.083447] usb 6-1: SerialNumber: 5B7402949950
  [  111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected
  [  111.157882] scsi host6: usb-storage 6-1:1.0
  [  111.158826] usbcore: registered new interface driver usb-storage
  [  111.174387] usbcore: registered new interface driver uas
  [  112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP 
PQ: 0 ANSI: 0 CCS
  [  112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0
  [  112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 
GB/1.92 GiB)
  [  112.443462] sd 6:0:0:0: [sdb]

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

apport information

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

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

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

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Seth Forshee 
(sforshee)

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

[Kernel-packages] [Bug 1761557] Re: Qualcom QCA6174 - regdomain: 0x5f

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Yu Kei (office-liquid-light)

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

apport information

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

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1757166] Re: linux-aws: 4.15.0-1002.2 -proposed tracker

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

** This bug has been marked a duplicate of bug 1761179
   linux-aws: 4.15.0-1003.3 -proposed tracker

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

Title:
  linux-aws: 4.15.0-1002.2 -proposed tracker

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1757166/+subscriptions

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

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

apport information

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

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1761438] Re: linux: 4.4.0-120.144 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1761438

Title:
  linux: 4.4.0-120.144 -proposed tracker

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

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

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

  backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial)
  derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 
(linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761438/+subscriptions

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-10 Thread Gordon Lack

I've tested the artful kernel on a UEFI system (and tracked own how the
signed kernel is produced from the unsigned on in the debs at he same
time - see #76).

It fixes the issue (tag already changed).

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in intel-microcode source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Some systems experience kernel lockups after updating to the latest 
intel-microcode
 package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
 it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
 may occur during package installation (disable IBPB by writing 0 to
 /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
 likely occur just after booting the system up as the lock screen is 
displayed.

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
 relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
     https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
     
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1761557] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1761557/+attachment/5109281/+files/ProcEnviron.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1762719] [NEW] System Z {kernel} UBUNTU18.04 wrong kernel config

Public bug reported:

Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic) is
not OK, because both security mechanisms nobp AND expoline are enabled:

CONFIG_KERNEL_NOBP=y
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
# CONFIG_EXPOLINE_MEDIUM is not set
CONFIG_EXPOLINE_FULL=y

If the kernel is compiled with a gcc that can generate expoline thunks
the correct config is as follows:

# CONFIG_KERNEL_NOBP is not set
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
# CONFIG_EXPOLINE_MEDIUM is not set
CONFIG_EXPOLINE_FULL=y

Alternatively the auto-detection patch can be used which is upstream as
of today:

commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

s390: add automatic detection of the spectre defense

Automatically decide between nobp vs. expolines if the spectre_v2=auto
kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.

The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
can be overruled with the nobp, nospec and spectre_v2 kernel parameters.

If this patch is used, then the correct config is

# CONFIG_KERNEL_NOBP is not set
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
CONFIG_EXPOLINE_AUTO=y
# CONFIG_EXPOLINE_FULL is not set

This patch goes together with three others, so a total of four patches
would be needed for the latest-and-greated solution:

b2e2f43a01bace1a25bdbae04c9f9846882b727a
6e179d64126b909f0b288fa63cdbf07c531e9b1d
bc035599718412cfba9249aa713f90ef13f13ee9
d424986f1d6b16079b3231db0314923f4f8deed1

** Affects: ubuntu-z-systems
 Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-166584 severity-critical 
targetmilestone-inin1804

** Tags added: architecture-s39064 bugnameltc-166584 severity-critical
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

[Kernel-packages] [Bug 1762719] [NEW] System Z {kernel} UBUNTU18.04 wrong kernel config

2018-04-10 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic) is
not OK, because both security mechanisms nobp AND expoline are enabled:

CONFIG_KERNEL_NOBP=y
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
# CONFIG_EXPOLINE_MEDIUM is not set
CONFIG_EXPOLINE_FULL=y

If the kernel is compiled with a gcc that can generate expoline thunks
the correct config is as follows:

# CONFIG_KERNEL_NOBP is not set
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
# CONFIG_EXPOLINE_MEDIUM is not set
CONFIG_EXPOLINE_FULL=y

Alternatively the auto-detection patch can be used which is upstream as
of today:

commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

s390: add automatic detection of the spectre defense

Automatically decide between nobp vs. expolines if the spectre_v2=auto
kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.

The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
can be overruled with the nobp, nospec and spectre_v2 kernel parameters.

If this patch is used, then the correct config is

# CONFIG_KERNEL_NOBP is not set
CONFIG_EXPOLINE=y
# CONFIG_EXPOLINE_OFF is not set
CONFIG_EXPOLINE_AUTO=y
# CONFIG_EXPOLINE_FULL is not set

This patch goes together with three others, so a total of four patches
would be needed for the latest-and-greated solution:

b2e2f43a01bace1a25bdbae04c9f9846882b727a
6e179d64126b909f0b288fa63cdbf07c531e9b1d
bc035599718412cfba9249aa713f90ef13f13ee9
d424986f1d6b16079b3231db0314923f4f8deed1

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-166584 severity-critical 
targetmilestone-inin---
-- 
System Z {kernel} UBUNTU18.04 wrong kernel config
https://bugs.launchpad.net/bugs/1762719
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 1761557] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1761557/+attachment/5109286/+files/UdevDb.txt

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

Title:
  Qualcom QCA6174 - regdomain: 0x5f

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  It looks like this bug remained for some time (Month?) and still exist. Some 
computers with the QCA6174 will have this and stuck with wrong country code. As 
far as I have learned from several threads e.g.:
  https://ubuntuforums.org/showthread.php?t=2384640
  https://patchwork.kernel.org/patch/9951857/
  it has to do with a 'regd_common.h' patch. Please have a look at the threads.
  The problem appears with Ubuntu 18,04, where Samsung Book computers are 
affected.

  Best regards
  Yu Kei
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ulrich 1242 F pulseaudio
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=f111ef48-6c46-41f4-8fbb-714c9839669c
  InstallationDate: Installed on 2018-04-01 (9 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Galaxy Book 10.6
  Package: linux-firmware 1.173
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=b471f2a3-8e4a-46f9-8fe4-196ba8c6a024 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01HAD.005.170613.WY.1108
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W620NZKBDBT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8879A29-C01-G001-S0001+10.0.15063
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01HAD.005.170613.WY.1108:bd06/13/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook10.6:pvrP01HAD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W620NZKBDBT:rvrSGL8879A29-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 10.6
  dmi.product.version: P01HAD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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