date:20180301

Can you try latest Bionic Daily image?

Also, do your Precision 5520 and XPS 15 9560 have the same display
resolution?

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

Title:
TB16 dock freezes X on hotplug when used with external displays

Status in Dell Sputnik:
New
Status in linux package in Ubuntu:
Confirmed

Bug description:
Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux
REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released
12/15/2017. If it can be of any help, I can get this tested on an XPS
9560 (GTX 1050) too.

Steps to reproduce:

1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI
cables are used, but I doubt that it matters.
2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME.
3. Select nVidia GPU in PRIME settings, reboot if needed.
4. Either boot with the dock connected or connect it after booting into user
session.
5. Set up monitors if necessary. At this point everything should be working
fine.
6. Disconnect the dock, give it a moment to adjust to the new window layout
etc.
7. Re-connect the dock. Within a few seconds laptop screen should freeze and
external monitors should remain blank, as if not connected.
8. Disconnect the dock. Within a few seconds laptop screen should unfreeze.
There is a small chance that it won't if you repeat this procedure multiple
times.

Errors in dmesg indicate that i915 driver is somehow involved:

[ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF B idle bit
[ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out
waiting for DP idle patterns
[ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting
for DDI BUF C idle bit

The kernel logs are flooded with these between steps 7 and 8 above.

This behaviour does not occur when Intel GPU is selected in PRIME
settings or when nouveau is used. However, nouveau performance leaves
a lot to be desired, particularly with 3D acceleration in Windows 10
VMs.

I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make
any difference.

Other reports that may be related:

https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a
-docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes-
hangs-the-whole-machine/ - same error messages

https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189
- "Connecting and disconnecting the TB16 sometimes freeze the laptop."

https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466
- "Hot-plugging the screen does not work."
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gboiko 2491 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c
InstallationDate: Installed on 2017-10-01 (149 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp.
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic
root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0
biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7
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.170
Tags: xenial
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision

[Kernel-packages] [Bug 1752680] Re: Night light does not work in some cases

2018-03-01 Thread Daniel van Vugt

See also bug 1728342

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

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

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

Title:
  Night light does not work in some cases

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-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.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1752680/+subscriptions

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

[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)

Thanks for your testing!

Can you also try latest Ubuntu Bionic? We need to backport fixes if
Bionic also has this problem.

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

Title:
  USB hub stops working after suspend(s?)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On initial boot, my usb hub works fine, but after a (series of?)
  suspends, I stop being able to see devices that are plugged into it.
  journalctl output on plugging it in:

  Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, 
idProduct=005a
  Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found
  Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected
  Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= 
SRC=fe80::::a299:9bff:fe17:9047 
DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 
FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 
using xhci_hcd
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, 
idProduct=772a
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp.
  Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at 
usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.0438] 
manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7)
  Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: 
"/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1"
  Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP 
device
  Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
  Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from 
eth0
  Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1000)
  Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/jbarnett] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
31]
  Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
48]
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error 
executing command as another user: Not authorized
  Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This 
incident has been reported.
  Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1066] device 
(eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2'
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] 
devices added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2)
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1214] device 
added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2,
 iface: enx0050b647ede2): no ifupdown configuration found.
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1217] device 
(enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', 
internal state 'external')
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: 
link is not ready
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1274] 
keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired 
connection 4")
  Oct 31 07:08:37 spiny NetworkManager[11575]:   [1509458917.1284] 
settings: (enx0050b647ede2): created default wired connection 'Wired connection 
4'
  Oct 31 07:08:37 spiny systemd[1]: Starting 
systemd-resolved-update-resolvconf.service...
  Oct 31 07:08:37 spiny systemd[1]: Started 
systemd-resolved-update-resolvconf.service.
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 
using xhci_hcd
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, 
idProduct=0105
  Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3,

[Kernel-packages] [Bug 1738263] Re: Touchpad not working and locking CPU

@Luke,

I think it's better to file separate bugs for each non-working device,
so we can tackle it one by 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/1738263

Title:
  Touchpad not working and locking CPU

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Notebook: ASUS GL703VD
  Touchpad: probably ELAN clickpad

  it seems to be connected to i2c bus

  the modules loaded are elan_i2c and multitouch_hid

  the multitouch hid module take almost 100% of cpu and the mouse cursor
  moves badly (loosing it for a second or 2 then resuming) also feature
  clicks and doubleclicks and sensitivity problems.

  doing rmmod hid-multitouch.ko (or rmmod multitouch_hid) and
  blacklisting the module solves the cpu problem but obviously the
  touchoad is dead.

  SEVERITY VERY HIGH
  It probably affects many other ASUS models.

  (the touchpad works perfectly in windows 10 by the way)

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

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

[Kernel-packages] [Bug 1752680] Re: Night light does not work in some cases

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Night light does not work in some cases

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-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.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1752680/+subscriptions

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

[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged

If you use HWE kernel (v4.13 based), you will get this update really
soon.

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

Title:
  [Asus UX360UA] battery status in unity-panel is not changing when
  battery is being charged

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, 
alongside with Windows 10. I've already installed the updates meanwhile.

  When I start charging my computer the battery icon on the unity-panel
  is not changing (it stays in the 98% complete).

  This is strange because this is a fresh installation so I didn't change any 
configuration yet. Also, when I tried this ubuntu in the live pen, I noticed 
that the icon changed when I started charging the laptop. That's why I think it 
is a bug.
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tjiagom1806 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
  InstallationDate: Installed on 2017-02-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-62-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/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX360UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

The graphic card is "GeForce GTX 1060 Mobile", which I don't think
nouveau has good support (yet).

Try to use proprietary Nvidia driver.

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

Title:
  The brightness of the screen cannot be adjusted with either the
  buttons or the slider.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness is always at 100% and cannot be adjusted with either the FN
  brightness buttons or the Unity top bar slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  albertoinet   1199 F pulseaudio
   /dev/snd/controlC0:  albertoinet   1199 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 20:49:16 2018
  HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f
  InstallationDate: Installed on 2018-02-25 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Micro-Star International Co., Ltd. GT72VR 7RD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1785IMS.30E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1785
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.family: GT
  dmi.product.name: GT72VR 7RD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2018-03-01 Thread Samir Tuffi Saliba Junior

I had Ubuntu 16.04 and Windows 10 dual-boot and experienced this bug.
Formatted my DELL-Vostro14, installed Mint and I'm experiencing this once again.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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

[Kernel-packages] [Bug 1752574] Re: Thunderbolt NULL pointer dereference in linux 4.15

Please update BIOS and TBT firmware. It's more likely to be a firmware
issue.

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

Title:
  Thunderbolt NULL pointer dereference in linux 4.15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.994565] thunderbolt :09:00.0: enabling device ( -> 0002)
  [0.994957] thunderbolt :09:00.0: NHI initialized, starting thunderbolt
  [0.994961] thunderbolt :09:00.0: allocating TX ring 0 of size 10
  [0.994983] thunderbolt :09:00.0: allocating RX ring 0 of size 10
  [0.994999] thunderbolt :09:00.0: control channel created
  [0.994999] thunderbolt :09:00.0: control channel starting...
  [0.995000] thunderbolt :09:00.0: starting TX ring 0
  [0.995018] thunderbolt :09:00.0: enabling interrupt at register 
0x38200 bit 0 (0x0 -> 0x1)
  [0.995018] thunderbolt :09:00.0: starting RX ring 0
  [0.995033] thunderbolt :09:00.0: enabling interrupt at register 
0x38200 bit 12 (0x1 -> 0x1001)
  [0.995046] thunderbolt :09:00.0: starting ICM firmware
  [0.995060] BUG: unable to handle kernel NULL pointer dereference at 
0980
  [0.995065] IP: pci_write_config_dword+0x5/0x30
  [0.995066] PGD 0 P4D 0 
  [0.995068] Oops:  [#1] SMP PTI
  [0.995069] Modules linked in: thunderbolt(+) ahci(+) ipmi_devintf libahci 
ipmi_msghandler video fjes(-)
  [0.995074] CPU: 6 PID: 214 Comm: systemd-udevd Not tainted 
4.15.0-10-generic #11-Ubuntu
  [0.995075] Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 
TH/Z170X-UD5 TH-CF, BIOS F22d 12/01/2017
  [0.995077] RIP: 0010:pci_write_config_dword+0x5/0x30
  [0.995078] RSP: 0018:9e58839779e0 EFLAGS: 00010296
  [0.995079] RAX: 4126 RBX:  RCX: 
0050
  [0.995080] RDX: 0200 RSI: 0034 RDI: 

  [0.995081] RBP: 9e5883977a18 R08: 0200 R09: 
0330
  [0.995082] R10: 2000 R11:  R12: 

  [0.995083] R13: 0050 R14: 92354e146f28 R15: 

  [0.995084] FS:  7f86f2204440() GS:92357ed8() 
knlGS:
  [0.995085] CS:  0010 DS:  ES:  CR0: 80050033
  [0.995086] CR2: 0980 CR3: 00080d1ce004 CR4: 
003606e0
  [0.995087] DR0:  DR1:  DR2: 

  [0.995088] DR3:  DR6: fffe0ff0 DR7: 
0400
  [0.995089] Call Trace:
  [0.995094]  ? pcie2cio_write+0x40/0x80 [thunderbolt]
  [0.995098]  icm_driver_ready+0x178/0x270 [thunderbolt]
  [0.995101]  ? tb_ctl_start+0x50/0x90 [thunderbolt]
  [0.995105]  tb_domain_add+0x79/0x100 [thunderbolt]
  [0.995108]  nhi_probe+0x186/0x300 [thunderbolt]
  [0.995110]  local_pci_probe+0x47/0xa0
  [0.995111]  pci_device_probe+0x145/0x1b0
  [0.995114]  driver_probe_device+0x31e/0x490
  [0.995116]  __driver_attach+0xa7/0xf0
  [0.995118]  ? driver_probe_device+0x490/0x490
  [0.995119]  bus_for_each_dev+0x70/0xc0
  [0.995121]  driver_attach+0x1e/0x20
  [0.995123]  bus_add_driver+0x1c7/0x270
  [0.995124]  ? 0xc03a9000
  [0.995125]  driver_register+0x60/0xe0
  [0.995126]  ? 0xc03a9000
  [0.995128]  __pci_register_driver+0x5a/0x60
  [0.995131]  nhi_init+0x2d/0x1000 [thunderbolt]
  [0.995133]  do_one_initcall+0x52/0x1a0
  [0.995135]  ? _cond_resched+0x19/0x40
  [0.995138]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [0.995140]  ? do_init_module+0x27/0x209
  [0.995141]  do_init_module+0x5f/0x209
  [0.995143]  load_module+0x191e/0x1f10
  [0.995146]  ? ima_post_read_file+0x96/0xa0
  [0.995148]  SYSC_finit_module+0xfc/0x120
  [0.995149]  ? SYSC_finit_module+0xfc/0x120
  [0.995151]  SyS_finit_module+0xe/0x10
  [0.995152]  do_syscall_64+0x76/0x130
  [0.995154]  entry_SYSCALL_64_after_hwframe+0x21/0x86
  [0.995155] RIP: 0033:0x7f86f1af3a49
  [0.995156] RSP: 002b:7ffdedfa4478 EFLAGS: 0246 ORIG_RAX: 
0139
  [0.995157] RAX: ffda RBX: 559d3ffde790 RCX: 
7f86f1af3a49
  [0.995158] RDX:  RSI: 7f86f17df0e5 RDI: 
0005
  [0.995159] RBP: 7f86f17df0e5 R08:  R09: 
7ffdedfa4590
  [0.995160] R10: 0005 R11: 0246 R12: 

  [0.995161] R13: 559d3ffedbf0 R14: 0002 R15: 
559d3ffde790
  [0.995162] Code: 87 c0 00 00 00 b9 04 00 00 00 48 89 e5 48 8b 40 20 e8 d0 
45 72 00 5d c3 b8 87 00 00 00 c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <48> 8b 
8f 80 09 00 00 83 e1 01 75 0b 55 48 89 e5 e8 a6 ff ff ff 
  [0.995182] RIP:

[Kernel-packages] [Bug 1752785] [NEW] package linux-image-4.15.0-10-generic 4.15.0-10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 8 when I try to dist-

2018-03-01 Thread Nicolás

Public bug reported:

The link /initrd.img is a dangling linkto /boot/initrd.img-4.15.0-10-generic
vmlinuz(/boot/vmlinuz-4.15.0-10-generic
) points to /boot/vmlinuz-4.15.0-10-generic
 (/boot/vmlinuz-4.15.0-10-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.15.0-10-generic.postinst line 491.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.15.0-10-generic 
/boot/vmlinuz-4.15.0-10-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.15.0-10-generic 
/boot/vmlinuz-4.15.0-10-generic
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
Error! Bad conf file.
File: 
does not represent a valid dkms.conf file.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kosciuk2487 F pulseaudio
 /dev/snd/controlC0:  kosciuk2487 F pulseaudio
Date: Fri Mar  2 01:08:32 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 8
HibernationDevice: RESUME=UUID=7eeb3a8c-066e-4883-9f70-6d2fa7cf0738
InstallationDate: Installed on 2013-08-18 (1657 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=80324639-7326-4734-8b10-41f54ca524f3 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions: grub-pc 2.02-2ubuntu7
RfKill:
 
SourcePackage: dkms
Title: package linux-image-4.15.0-10-generic 4.15.0-10.11 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
8
UpgradeStatus: Upgraded to bionic on 2018-03-01 (0 days ago)
dmi.bios.date: 03/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1202
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A88-V EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1202:bd03/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-10-generic 4.15.0-10.11 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 8 when I try to dist-upgrade

Status in dkms package in Ubuntu:
  New

Bug description:
  The link /initrd.img is a dangling linkto /boot/initrd.img-4.15.0-10-generic
  vmlinuz(/boot/vmlinuz-4.15.0-10-generic
  ) points to /boot/vmlinuz-4.15.0-10-generic
   (/boot/vmlinuz-4.15.0-10-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.15.0-10-generic.postinst line 491.
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.15.0-10-generic /boot/vmlinuz-4.15.0-10-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.15.0-10-generic 
/boot/vmlinuz-4.15.0-10-generic
  dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
  dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
  dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
  Error! Bad conf file.
  File: 
  does not represent a valid dkms.conf file.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kosciuk2487 F

[Kernel-packages] [Bug 1750385] Re: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel

Please do check that, thanks!

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

Title:
  Poor wifi signal with RTL8723BE and 4.13.0-32 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using Linux Mint 18.3 alongside with the 4.13.0-32 kernel the
  wifi signal is really really poor (while almost sitting on the
  respective router) whereas with the 4.10.0-38 it works like charm.

  I had to use a configuration file for getting the wifi to work
  properly (/etc/modprobe.d/rtl8723be.conf: options rtl8723be fwlps=0
  ips=0 ant_sel=1) but chaning the antenna from 1 to 0 did not change
  anything with the 4.13 kernel.

  I am also running Manjaro Linux with the 4.14 kernel on my machine
  where the wifi is also working just fine (with antenna 0 though).

  cat /proc/version_signature:
  Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17

  (I tried using ubuntu-bug linux but it didn't work [The report belongs
  to a package that is not installed.])

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

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

[Kernel-packages] [Bug 1752550] Re: Failed to create KVM on Trusty ppc64le, no supported architecture for os type 'hvm'

2018-03-01 Thread Po-Hsu Lin

It looks like this might be related to bug 1452016, there is no ppc64le
specific template available on Trusty.

A simple copy-and-paste to create a template from Bionic still can't
make this work.

BTW, there is no /dev/kvm on Trusty ppc64le

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

Title:
  Failed to create KVM on Trusty ppc64le, no supported architecture for
  os type 'hvm'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to use uvtool to create a KVM instance with Trusty kernel on a
  ppc64le system will fail with:

  uvt-kvm: error: libvirt: internal error: no supported architecture for
  os type 'hvm'

  Command:
  uvt-kvm create kvm-test release=xenial arch=ppc64el

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-142-generic 3.13.0-142.191
  ProcVersionSignature: Ubuntu 3.13.0-142.191-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-142-generic ppc64le
  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'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CurrentDmesg:

  Date: Thu Mar  1 11:09:14 2018
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro 
console=hvc0
  ProcLoadAvg: 1.18 0.67 0.28 1/1074 8837
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 6459 00:11:43064 0 0
   2: FLOCK  ADVISORY  WRITE 2334 00:11:27831 0 EOF
   3: POSIX  ADVISORY  WRITE 2264 00:11:35027 0 EOF
   4: POSIX  ADVISORY  WRITE 2387 00:11:35925 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 3.13.0-142-generic (buildd@bos02-ppc64el-009) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #191-Ubuntu SMP Fri Feb 2 
12:12:31 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-142-generic N/A
   linux-backports-modules-3.13.0-142-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_freq:
   min: 3.694 GHz (cpu 124)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No firmware implementation of function
  cpu_smt: SMT=8

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

2018-03-01 Thread Manoj Iyer

Merlin system cert results.

** Attachment added: "results of cert on merlin"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066621/+files/submission_2018-03-02T03.59.13.971794.html

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

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

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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1752772

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

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

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1752772] [NEW] r8169 ethernet card don't work after returning from suspension

2018-03-01 Thread Leonardo Müller

Public bug reported:

I have noticed that the network stopped working on my desktop after I've
suspended the system and woke it up. On dmesg there are messages like:

[  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[  150.944101] do_IRQ: 3.37 No irq handler for vector
[  150.944105] r8169 :01:00.0 enp1s0: link down
[  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

When using Xenial (from a different install), this problem is not
happening. This is happening on Bionic.

There are only two ways to restore connectivity: 
1) Reboot the system;
2) Remove the r8169 module and reinsert it with modprobe.

The motherboard is a AsRock H55M-LE and the Ethernet controller is:

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.172
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Mar  2 00:21:57 2018
Dependencies:
 
InstallationDate: Installed on 2018-02-26 (3 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

2018-03-01 Thread Daniel van Vugt

I can reproduce the bug in 16.04 but it seems to be fixed in 18.04:

$ echo '' | bluetoothctl
No agent is registered
$

$ bluetoothctl < /dev/null
[bluetooth]# quitt to bluetoothd...
No agent is registered
$

I'm going to declare this fix released and nominate 17.10 for a fix
(whatever the fix would be).

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

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

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

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

Re: [Kernel-packages] [Bug 1751518] Re: video blanks after boot with dual monitors

2018-03-01 Thread Alan Bland

I made a fresh install.  The problem is gone.

There were some other weird behaviors.  So I made a fresh install.  
Which worked.  It continues to work after updating the kernel.

I don't know what was wrong with the previous installation.  The 
computer seems to be working well now.

Thanks for the reply.

I will look into testing the 4.16 kernel, but my time is limited.  It 
won't be soon.

AB


On 02/27/2018 02:47 PM, Joseph Salisbury wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.16 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc3
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>

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

Title:
  video blanks  after boot with dual monitors

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed fresh from Mint 18.3 ISO today on my latitude E6410.  After the 
no network install I set up a second monitor.  Then I applied a bunch of level 
1 and 2 updates.  There were four level 3 updates: systemd 229-4ubuntu21.1, 
linix-firmware 1.157.16; linux-libc-dev 4.4.0-116.140, and linuxkernel 
4.13.0-36.40-16.04.1.  
  I installed them separately and rebooted after each one.  After the kernel 
update the system booted up and briefly showed the sqaure mint logo then both 
screens went dark.  

  I ran ubuntu-bug linux it reports the ** Problem in linux-
  image-4.13.0-36-generic

  The problem cannot be reported:

  This is not an official Linux package. Please remove any third party
  package and try again.

  
  cat /proc/version_signature 
  Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  alan@alan-Latitude-E6410 ~ $ 

  I am booting now with the 4.10 version kernel that came with the iso.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1777 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=d536e87b-7a3c-48dc-9e30-ed32fc32e74a
  InstallationDate: Installed on 2018-02-24 (1 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  Lsusb:
   Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E6410
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=b2b6da50-3200-491a-95d1-eeab4794941c ro quiet splash vt.handoff=7
  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.16
  Tags:  sylvia
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0667CC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2011:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1748470] Re: Spectre V2 : System may be vulnerable to spectre v2

2018-03-01 Thread Lee

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

user@server2:~$ tail /sys/devices/system/cpu/vulnerabilities/*
==> /sys/devices/system/cpu/vulnerabilities/meltdown <==
Mitigation: PTI

==> /sys/devices/system/cpu/vulnerabilities/spectre_v1 <==
Mitigation: __user pointer sanitization

==> /sys/devices/system/cpu/vulnerabilities/spectre_v2 <==
Mitigation: Full generic retpoline - vulnerable module loaded

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

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

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

I've seen a couple crashes on a ThunderX CRB1S system - though at this
point I don't have reason to believe it is related to KPTI. This system
happened to be installed with LVM + crypted home, and we haven't ran the
cert tests on such a config before. After the remaining tests complete,
I plan to re-run with the pre-kpti kernel on this config, as well as
running cert on the "usual" config w/ a kpti kernel. I was only able to
capture the console of one of the crashes, I'll attach it here.

I also have a cert run still in-progress from a Gigabyte R120. This
system is very similar to the CRB1S, and has not seen any problems yet.

** Attachment added: "thunderx panic console log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066573/+files/console.log

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

** Attachment added: "sabre test results - all errors expected"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066572/+files/submission_2018-03-01T15.11.01.312793.html

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1737761] Re: zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2

2018-03-01 Thread Launchpad Bug Tracker

This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu19

---
zfs-linux (0.6.5.6-0ubuntu19) xenial; urgency=medium

  * Add ZFS 0.7.0 kernel ioctl binary compat shim (LP: #1737761)
Detect ZFS kernel driver version and copy zfs ioctl command to the
newer ZFS 0.7.0 ioctl command layout.

 -- Colin Ian King   Mon, 19 Feb 2017 13:04:11
+0100

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  == SRU Justification, Xenial, Artful ==

  Running ZFS userspace utils with newer 0.7.x ZFS kernel drivers breaks
  ZFS send/receive because of changes in the ioctl command structure.

  == Testcase ==

  ubuntu ADT ZFS tests autotests/client/tests/ubuntu-zfs-smoke-tests
  will show a failure in ZFS SEND, with userspace zfs tools segfaulting.

  == Fix ==

  Fix is to detect if ZFS kernel driver is version 0.7.x and copy the
  0.6.5.x zfs ioctl command structure to a ZFS 0.7.x version, call the
  ioctl() and then copy the result back.

  == Regression Potential ==

  This will only affect the ZFS ioctl interface and this can be fully
  tested using the ZFS autotests with 0.7.0 and 0.6.5.x ZFS enabled
  kernels to check for the compatibility change regressions.

  --

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/z/zfs-linux/20171212_032601_d0613@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/arm64/z/zfs-linux/20171212_020008_d0613@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/z/zfs-linux/20171212_024359_d0613@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/z/zfs-linux/20171212_032349_d0613@/log.gz

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

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

[Kernel-packages] [Bug 1752061] Re: nfp: prioritize stats updates

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

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

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

Thanks in advance!

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

Title:
  nfp: prioritize stats updates

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

Bug description:
  This is a backport request from Netronome for Ubuntu 18.04 LTS.

  Description: Previously it was possible to interrupt processing stats updates 
because they were handled in a work queue. Interrupting the stats updates could 
lead to a situation where we backup the control message queue. This patch
  moves the stats update processing out of the work queue to be processed as 
soon as hardware sends a request.

  The following fix for the above has been accepted into upstream for
  v4.16. This ticket requests backporting it to Ubuntu 18.04 LTS.

  01c15e93a78c ("nfp: flower: prioritize stats updates")

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

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

[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic

2018-03-01 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-firmware - 1.172

---
linux-firmware (1.172) bionic; urgency=medium

  * Rebase against 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
7344ec9e1df9e27d105ed48d2db99e22370236de
- nfp: update Agilio SmartNIC firmware to rev 2.0.4
- qed: Add firmwares 8.30.12.0 and 8.10.9.0
- rtl_bt: Add firmware and configuration files for the Bluetooth parts of 
RTL8821C and RTL8723D
- ath10k: QCA4019 hw1.0: update firmware-5.bin to 10.4-3.5.3-00053
- ath10k: QCA4019 hw1.0: update board-2.bin
- ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1
- ath10k: QCA6174 hw3.0: update board-2.bin
- ath10k: QCA9377 hw1.0: update firmware-5.bin to 
WLAN.TF.1.0-2-QCATFSWPZ-5
- ath10k: QCA9887 hw1.0: update firmware-5.bin to 10.2.4-1.0-00037
- ath10k: QCA9888 hw2.0: update firmware-5.bin to 10.4-3.5.3-00053
- ath10k: QCA988X hw2.0: update firmware-5.bin to 10.2.4-1.0-00037
- ath10k: QCA9984 hw1.0: update firmware-5.bin to 10.4-3.5.3-00053

  * Missing firmware in linux-image-4.15.0-10-generic (LP: #1751266)
- Restore firmware files previously duplicated in the kernel package
- Add restored firmware files to nic-firmware.lst and scsi-firmware.lst

 -- Seth Forshee   Thu, 01 Mar 2018 15:30:32
-0600

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Missing firmware in linux-image-4.15.0-10-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  linux-image-4.15.0-10-generic doesn't have the firmware that linux-
  image-4.13.0-32-generic has. It doesn't have any of the files that are
  present in 4.13 in /lib/firmware/4.13.0-32-generic/.

  For me, this means i can boot 4.15, but my network wont work because
  of:

  kernel: [   13.468996] bnx2 :0b:00.0: Direct firmware load for 
bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
  kernel: [   13.468998] bnx2: Can't load firmware file 
"bnx2/bnx2-mips-09-6.2.1b.fw"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 feb 23 13:12 seq
   crw-rw 1 root audio 116, 33 feb 23 13:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  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:
  Date: Fri Feb 23 13:50:38 2018
  InstallationDate: Installed on 2018-02-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM System x3550 M3 -[7944S77]-
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E158AUS-1.16]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: System x3550 M3 -[7944S77]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

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

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

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

Title:
  nouveau module can't be loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Module nouveou can't be loaded. I get the following error message when
  I try to load it manually:

  # modprobe nouveau
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-lowlatency 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lvella 1453 F pulseaudio
   /dev/snd/controlC0:  lvella 1453 F pulseaudio
   /dev/snd/controlC1:  lvella 1453 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Mar  1 20:37:06 2018
  HibernationDevice: RESUME=UUID=3f064780-2aeb-44b4-a8a3-21e590bd1b8f
  InstallationDate: Installed on 2016-06-02 (637 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-lowlatency.efi.signed 
root=UUID=f127c524-7b47-4ff1-b1d6-620ed6f14a29 ro noprompt persistent quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-lowlatency N/A
   linux-backports-modules-4.15.0-10-lowlatency  N/A
   linux-firmware1.171
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-28 (1 days ago)
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd04/20/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1752748] [NEW] nouveau module can't be loaded

2018-03-01 Thread Lucas Clemente Vella

Public bug reported:

Module nouveou can't be loaded. I get the following error message when I
try to load it manually:

# modprobe nouveau
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-lowlatency 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
Uname: Linux 4.15.0-10-lowlatency x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  lvella 1453 F pulseaudio
 /dev/snd/controlC0:  lvella 1453 F pulseaudio
 /dev/snd/controlC1:  lvella 1453 F pulseaudio
CurrentDesktop: XFCE
Date: Thu Mar  1 20:37:06 2018
HibernationDevice: RESUME=UUID=3f064780-2aeb-44b4-a8a3-21e590bd1b8f
InstallationDate: Installed on 2016-06-02 (637 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 lono wireless extensions.
 
 enp5s0no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-lowlatency.efi.signed 
root=UUID=f127c524-7b47-4ff1-b1d6-620ed6f14a29 ro noprompt persistent quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-10-lowlatency N/A
 linux-backports-modules-4.15.0-10-lowlatency  N/A
 linux-firmware1.171
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-02-28 (1 days ago)
dmi.bios.date: 04/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3701
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3701:bd04/20/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

Title:
  nouveau module can't be loaded

Status in linux package in Ubuntu:
  New

Bug description:
  Module nouveou can't be loaded. I get the following error message when
  I try to load it manually:

  # modprobe nouveau
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-lowlatency 4.15.0-10.11

[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged

2018-03-01 Thread tjiagoM

I see here that a fix was committed to Ubuntu Artful. Does this mean the
fix is specific for ubuntu distributions or there is a new kernel I will
be able to use with my ubuntu 16.04?

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

Title:
  [Asus UX360UA] battery status in unity-panel is not changing when
  battery is being charged

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, 
alongside with Windows 10. I've already installed the updates meanwhile.

  When I start charging my computer the battery icon on the unity-panel
  is not changing (it stays in the 98% complete).

  This is strange because this is a fresh installation so I didn't change any 
configuration yet. Also, when I tried this ubuntu in the live pen, I noticed 
that the icon changed when I started charging the laptop. That's why I think it 
is a bug.
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tjiagom1806 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
  InstallationDate: Installed on 2017-02-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-62-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/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX360UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

Title:
  Kernel deadlock when using cachefiles.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was using both a cifs share and a nfs share at the moment of the
  crash, both network filesystems get mounted by automount, seems that
  the bug happened at the cifs automatic umount. Machine froze and
  stopped responding pings from the network, not even sysrq keys worked,
  needed a hard power off. Kernel panic (at least what made to syslog)
  follows:

  Mar  1 19:34:04 xps kernel: [ 5497.617469] [ cut here 
]
  Mar  1 19:34:04 xps kernel: [ 5497.617472] kernel BUG at 
/build/linux-fQ94TU/linux-4.4.0/fs/fscache/cookie.c:639!
  Mar  1 19:34:04 xps kernel: [ 5497.617474] invalid opcode:  [#1] SMP 
  Mar  1 19:34:04 xps kernel: [ 5497.617475] Modules linked in: rpcsec_gss_krb5 
nfsv4 nfs drbg ansi_cprng md4 nls_utf8 cifs ccm bnep pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(
  OE) dm_cache_smq dm_cache dm_persistent_data dm_bio_prison zram dm_bufio 
lz4_compress libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 ath3k videobuf2_core btusb v4l2_com
  mon btrtl videodev btbcm btintel snd_usb_audio joydev media input_leds 
bluetooth snd_usbmidi_lib snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_hd
  a_codec_realtek snd_hda_codec_generic kvm dcdbas irqbypass snd_hda_intel arc4 
crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel ath9k 
aesni_intel snd_hda_core aes_x86_64 lrw sn
  d_hwdep gf128mul glue_helper snd_pcm ath9k_common ablk_helper ath9k_hw cryptd 
snd_seq_midi ath snd_seq_midi_event snd_rawmidi nvidia_uvm(POE) mac80211 
snd_seq snd_seq_device snd_timer cfg802
  11 serio_raw snd mei_me mei soundcore lpc_ich shpchp mac_hid binfmt_misc 
cachefiles nfsd fscache auth_rpcgss parport_pc nfs_acl lockd ppdev lp grace 
sunrpc parport autofs4 btrfs xor uas usb_
  storage raid6_pq hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse 
fb_sys_fops ahci r8169 drm libahci mii video 
  fjes
  Mar  1 19:34:04 xps kernel: [ 5497.617515] CPU: 2 PID: 20454 Comm: umount 
Tainted: P   OE   4.4.0-116-generic #140-Ubuntu
  Mar  1 19:34:04 xps kernel: [ 5497.617516] Hardware name: Dell Inc. XPS 
8700/0KWVT8, BIOS A08 04/16/2014
  Mar  1 19:34:04 xps kernel: [ 5497.617517] task: 88034802c600 ti: 
88029858c000 task.ti: 88029858c000
  Mar  1 19:34:04 xps kernel: [ 5497.617518] RIP: 0010:[]  
[] __fscache_cookie_put+0x3a/0x40 [fscache]
  Mar  1 19:34:04 xps kernel: [ 5497.617525] RSP: 0018:88029858fd98  
EFLAGS: 00010282
  Mar  1 19:34:04 xps kernel: [ 5497.617526] RAX: 0001 RBX: 
8802e00244d0 RCX: 0034
  Mar  1 19:34:04 xps kernel: [ 5497.617527] RDX: 0001 RSI: 
8802e0024528 RDI: 8802e0024528
  Mar  1 19:34:04 xps kernel: [ 5497.617528] RBP: 88029858fda0 R08: 
88041ec972c0 R09: 0001
  Mar  1 19:34:04 xps kernel: [ 5497.617528] R10: 0010 R11: 
 R12: 8802dde8f000
  Mar  1 19:34:04 xps kernel: [ 5497.617529] R13: 1f39 R14: 
 R15: 88034802cca0
  Mar  1 19:34:04 xps kernel: [ 5497.617531] FS:  7f93632b5840() 
GS:88041ec8() knlGS:
  Mar  1 19:34:04 xps kernel: [ 5497.617532] CS:  0010 DS:  ES:  CR0: 
80050033
  Mar  1 19:34:04 xps kernel: [ 5497.617533] CR2: 2205d5e14000 CR3: 
000293ff6000 CR4: 00160670
  Mar  1 19:34:04 xps kernel: [ 5497.617534] Stack:
  Mar  1 19:34:04 xps kernel: [ 5497.617535]  8802e0024528 88029858fdb8 
c10a6517 880348d55800
  Mar  1 19:34:04 xps kernel: [ 5497.617536]  88029858fdd0 c1854232 
880348d55800 88029858fdf8
  Mar  1 19:34:04 xps kernel: [ 5497.617538]  c182d3e0 8800a1c7ce40 
880348d55000 880348d55008
  Mar  1 19:34:04 xps kernel: [ 5497.617548] Call Trace:
  Mar  1 19:34:04 xps kernel: [ 5497.617552]  [] 
__fscache_relinquish_cookie+0x87/0x120 [fscache]
  Mar  1 19:34:04 xps kernel: [ 5497.617572]  [] 
cifs_fscache_release_super_cookie+0x32/0x90 [cifs]
  Mar  1 19:34:04 xps kernel: [ 5497.617580]  [] 
cifs_put_tcon+0x100/0x180 [cifs]
  Mar  1 19:34:04 xps kernel: [ 5497.617587]  [] 
cifs_put_tlink+0x47/0x60 [cifs]
  Mar  1 19:34:04 xps kernel: [ 5497.617595]  [] 
cifs_umount+0x5b/0xc0 [cifs]
  Mar  1 19:34:04 xps kernel: [ 5497.617602]  [] 
cifs_kill_sb+0x1e/0x30 [cifs]
  Mar  1 19:34:04 xps kernel: [ 5497.617605]  [] 
deactivate_locked_super+0x48/0x80
  Mar  1 19:34:04 xps kernel: [ 5497.617607]  [] 
deactivate_super+0x5c/0x60
  Mar  1 19:34:04 xps kernel: [

[Kernel-packages] [Bug 1666290] Re: package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to install/upgrade: »/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« ka

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to
  install/upgrade:
  »/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko
  .dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Automated bug report. No further information from my side

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-38-generic 4.8.0-38.41
  ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17
  Uname: Linux 4.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   linux-image-extra-4.8.0-38-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  roman  5925 F pulseaudio
   /dev/snd/controlC2:  roman  5925 F pulseaudio
   /dev/snd/controlC1:  roman  5925 F pulseaudio
   /dev/snd/controlC0:  roman  5925 F pulseaudio
  Date: Mon Feb 20 18:53:22 2017
  DpkgTerminalLog:
   Vorbereitung zum Entpacken von 
.../linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb ...
   Entpacken von linux-image-extra-4.8.0-38-generic (4.8.0-38.41) ...
   dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/linux-image-extra-4.8.0-38-generic_4.8.0-38.41_amd64.deb
 (--unpack):

»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
  ErrorMessage: 
»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
  HibernationDevice: RESUME=UUID=65743a1a-1279-417e-ab26-cd17b1baa629
  InstallationDate: Installed on 2017-01-29 (21 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-38-generic 
root=UUID=3d889fca-fb58-4d48-bfb6-61c9d6408e49 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.8.0-38-generic 4.8.0-38.41 failed to 
install/upgrade: 
»/lib/modules/4.8.0-38-generic/kernel/drivers/net/can/usb/esd_usb2.ko.dpkg-new« 
kann nicht geöffnet werden: Vorgang nicht zulässig
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1681168] Re: package linux-firmware 1.161.1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

** Changed in: linux-firmware (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  package linux-firmware 1.161.1 failed to install/upgrade: subprocess
  installed post-installation script was killed by signal (Terminated)

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  Linux upgrade failed at restart.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-firmware 1.161.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sat Apr  8 22:58:42 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2017-04-09 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.161.1 failed to install/upgrade: subprocess 
installed post-installation script was killed by signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1670154] Re: package linux-headers-4.8.0-39 (not installed) failed to install/upgrade: impossible d'ouvrir « /usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  package linux-headers-4.8.0-39 (not installed) failed to
  install/upgrade: impossible d'ouvrir « /usr/src/linux-
  headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: Opération non
  permise

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-headers-4.8.0-39 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uhuru  2394 F pulseaudio
   /dev/snd/controlC1:  uhuru  2394 F pulseaudio
   /dev/snd/controlC2:  uhuru  2394 F pulseaudio
  Date: Wed Mar  1 22:32:59 2017
  ErrorMessage: impossible d'ouvrir « 
/usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: 
Opération non permise
  HibernationDevice: RESUME=UUID=96b2f8e3-8186-46c4-8475-124db407e9ba
  InstallationDate: Installed on 2016-01-27 (402 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp5s8no wireless extensions.
  MachineType: Dell Inc. Dimension 9100
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic 
root=UUID=4c460bad-c68b-438c-aebc-70f7efc5103d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.8.0-39 (not installed) failed to 
install/upgrade: impossible d'ouvrir « 
/usr/src/linux-headers-4.8.0-39/include/uapi/drm/via_drm.h.dpkg-new »: 
Opération non permise
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0X8582
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/07/2006:svnDellInc.:pnDimension9100:pvr:rvnDellInc.:rn0X8582:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dimension 9100
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1752061] Re: nfp: prioritize stats updates

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

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

Title:
  nfp: prioritize stats updates

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

Bug description:
  This is a backport request from Netronome for Ubuntu 18.04 LTS.

  Description: Previously it was possible to interrupt processing stats updates 
because they were handled in a work queue. Interrupting the stats updates could 
lead to a situation where we backup the control message queue. This patch
  moves the stats update processing out of the work queue to be processed as 
soon as hardware sends a request.

  The following fix for the above has been accepted into upstream for
  v4.16. This ticket requests backporting it to Ubuntu 18.04 LTS.

  01c15e93a78c ("nfp: flower: prioritize stats updates")

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

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

[Kernel-packages] [Bug 1683376] Re: gstreamer-plugins-bad-i386 dependency error

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  gstreamer-plugins-bad-i386 dependency error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The problem here seems to be that the package is dependent upon itself.
  All the dependencies below are met and most are already installed including 
the last two.

  
  The following packages have unmet dependencies:

  gstreamer1.0-plugins-bad:i386: Depends: libc6 (>= 2.15) but 2.24-3ubuntu2 is 
to be installed
 Depends: libcurl3-gnutls (>= 7.16.2) but 
7.50.1-1ubuntu1.1 is to be installed
 Depends: libdvdnav4 (>= 4.1.3) but 5.0.3-1 is 
to be installed
 Depends: libdvdread4 (>= 4.1.3) but 5.0.3-1 is 
to be installed
 Depends: libgcc1 (>= 1:3.0) but 
1:6.2.0-5ubuntu12 is to be installed
 Depends: libglib2.0-0 (>= 2.40) but 
2.50.2-2ubuntu1 is to be installed
 Depends: libgstreamer-plugins-bad1.0-0 (= 
1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed
 Depends: libgtk-3-0 (>= 3.16.2) but 
3.20.9-1ubuntu2.1 is to be installed
 Depends: libgudev-1.0-0 (>= 146) but 1:230-3 
is to be installed
 Depends: libilmbase12 (>= 2.2.0) but 
2.2.0-11ubuntu2 is to be installed
 Depends: libjpeg8 (>= 8c) but 8c-2ubuntu8 is 
to be installed
 Depends: libmodplug1 (>= 1:0.8.8.5) but 
1:0.8.8.5-2 is to be installed
 Depends: libopenal1 (>= 1.14) but 1:1.17.2-1 
is to be installed
 Depends: libopenjp2-7 (>= 2.0.0) but 
2.1.1-1ubuntu0.1 is to be installed
 Depends: liborc-0.4-0 (>= 1:0.4.25) but 
1:0.4.26-1 is to be installed
 Depends: librsvg2-2 (>= 2.36.2) but 2.40.16-1 
is to be installed
 Depends: librtmp1 (>= 2.3) but 
2.4+20151223.gitfa8646d.1-1 is to be installed
 Depends: libsoundtouch1 (>= 1.9.2) but 1.9.2-2 
is to be installed
 Depends: libstdc++6 (>= 5.2) but 
6.2.0-5ubuntu12 is to be installed
 Depends: libusb-1.0-0 (>= 2:1.0.8) but 
2:1.0.20-1 is to be installed
 Depends: libwayland-client0 (>= 1.9.91) but 
1.11.0-2 is to be installed
 Depends: libx265-79 (>= 1.9) but 1.9-3 is to 
be installed
 Depends: libxml2 (>= 2.9.0) but 
2.9.4+dfsg1-2ubuntu0.1 is to be installed
 Depends: gstreamer1.0-plugins-bad-videoparsers 
(= 1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed
 Depends: gstreamer1.0-plugins-bad-faad (= 
1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed

  
  cat version.log
  Ubuntu 4.8.0-46.49-generic 4.8.17

  ubuntu 16.10
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   4322 F pulseaudio
   /dev/snd/controlC3:  mark   4322 F pulseaudio
   /dev/snd/controlC2:  mark   4322 F pulseaudio
   /dev/snd/controlC0:  mark   4322 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=3e34a9fd-33a3-4027-86ff-5151122c5379
  InstallationDate: Installed on 2010-03-14 (2590 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=bf8502af-6555-4b4c-a93f-11ee7121da7d ro quiet nosplash 
libata.force=noncq
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-46-generic N/A
   linux-backports-modules-4.8.0-46-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout floppy fuse libvirt

[Kernel-packages] [Bug 1752742] Re: Kernel deadlock when using cachefiles.

2018-03-01 Thread Daniel Ribeiro

cachefilesd.conf:
dir /cache/fscache
tag mycache
brun 10%
bcull 7%
bstop 3%
frun 10%
fcull 7%
fstop 3%
secctx system_u:system_r:cachefiles_kernel_t:s0

/cache is a separate ext4 partition, currently only cachefiles using it.

the cifs mount was using the following options:
//htpc/rootfs/ on /smb/htpc type cifs 
(rw,relatime,vers=1.0,cache=none,username=wyrm,domain=HTPC,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.5,unix,posixpaths,serverino,acl,fsc,noperm,rsize=65536,wsize=65536,echo_interval=60,actimeo=1,user=wyrm)

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

Title:
  Kernel deadlock when using cachefiles.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Was using both a cifs share and a nfs share at the moment of the
  crash, both network filesystems get mounted by automount, seems that
  the bug happened at the cifs automatic umount. Machine froze and
  stopped responding pings from the network, not even sysrq keys worked,
  needed a hard power off. Kernel panic (at least what made to syslog)
  follows:

  Mar  1 19:34:04 xps kernel: [ 5497.617469] [ cut here 
]
  Mar  1 19:34:04 xps kernel: [ 5497.617472] kernel BUG at 
/build/linux-fQ94TU/linux-4.4.0/fs/fscache/cookie.c:639!
  Mar  1 19:34:04 xps kernel: [ 5497.617474] invalid opcode:  [#1] SMP 
  Mar  1 19:34:04 xps kernel: [ 5497.617475] Modules linked in: rpcsec_gss_krb5 
nfsv4 nfs drbg ansi_cprng md4 nls_utf8 cifs ccm bnep pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(
  OE) dm_cache_smq dm_cache dm_persistent_data dm_bio_prison zram dm_bufio 
lz4_compress libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 ath3k videobuf2_core btusb v4l2_com
  mon btrtl videodev btbcm btintel snd_usb_audio joydev media input_leds 
bluetooth snd_usbmidi_lib snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_hd
  a_codec_realtek snd_hda_codec_generic kvm dcdbas irqbypass snd_hda_intel arc4 
crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel ath9k 
aesni_intel snd_hda_core aes_x86_64 lrw sn
  d_hwdep gf128mul glue_helper snd_pcm ath9k_common ablk_helper ath9k_hw cryptd 
snd_seq_midi ath snd_seq_midi_event snd_rawmidi nvidia_uvm(POE) mac80211 
snd_seq snd_seq_device snd_timer cfg802
  11 serio_raw snd mei_me mei soundcore lpc_ich shpchp mac_hid binfmt_misc 
cachefiles nfsd fscache auth_rpcgss parport_pc nfs_acl lockd ppdev lp grace 
sunrpc parport autofs4 btrfs xor uas usb_
  storage raid6_pq hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse 
fb_sys_fops ahci r8169 drm libahci mii video 
  fjes
  Mar  1 19:34:04 xps kernel: [ 5497.617515] CPU: 2 PID: 20454 Comm: umount 
Tainted: P   OE   4.4.0-116-generic #140-Ubuntu
  Mar  1 19:34:04 xps kernel: [ 5497.617516] Hardware name: Dell Inc. XPS 
8700/0KWVT8, BIOS A08 04/16/2014
  Mar  1 19:34:04 xps kernel: [ 5497.617517] task: 88034802c600 ti: 
88029858c000 task.ti: 88029858c000
  Mar  1 19:34:04 xps kernel: [ 5497.617518] RIP: 0010:[]  
[] __fscache_cookie_put+0x3a/0x40 [fscache]
  Mar  1 19:34:04 xps kernel: [ 5497.617525] RSP: 0018:88029858fd98  
EFLAGS: 00010282
  Mar  1 19:34:04 xps kernel: [ 5497.617526] RAX: 0001 RBX: 
8802e00244d0 RCX: 0034
  Mar  1 19:34:04 xps kernel: [ 5497.617527] RDX: 0001 RSI: 
8802e0024528 RDI: 8802e0024528
  Mar  1 19:34:04 xps kernel: [ 5497.617528] RBP: 88029858fda0 R08: 
88041ec972c0 R09: 0001
  Mar  1 19:34:04 xps kernel: [ 5497.617528] R10: 0010 R11: 
 R12: 8802dde8f000
  Mar  1 19:34:04 xps kernel: [ 5497.617529] R13: 1f39 R14: 
 R15: 88034802cca0
  Mar  1 19:34:04 xps kernel: [ 5497.617531] FS:  7f93632b5840() 
GS:88041ec8() knlGS:
  Mar  1 19:34:04 xps kernel: [ 5497.617532] CS:  0010 DS:  ES:  CR0: 
80050033
  Mar  1 19:34:04 xps kernel: [ 5497.617533] CR2: 2205d5e14000 CR3: 
000293ff6000 CR4: 00160670
  Mar  1 19:34:04 xps kernel: [ 5497.617534] Stack:
  Mar  1 19:34:04 xps kernel: [ 5497.617535]  8802e0024528 88029858fdb8 
c10a6517 880348d55800
  Mar  1 19:34:04 xps kernel: [ 5497.617536]  88029858fdd0 c1854232 
880348d55800 88029858fdf8
  Mar  1 19:34:04 xps kernel: [ 5497.617538]  c182d3e0 8800a1c7ce40 
880348d55000 880348d55008
  Mar  1 19:34:04 xps kernel: [ 5497.617548] Call Trace:
  Mar  1 19:34:04 xps kernel: [ 5497.617552]  [] 
__fscache_relinquish_cookie+0x87/0x120 [fscache]
  Mar  1 19:34:04 xps kernel: [ 5497.617572]  [] 
cifs_fscache_release_super_cookie+0x32/0x90 [cifs]
  Mar  1 19:34:04 xps kernel: [ 5497.617580]  [] 
cifs_put_tcon+0x100/0x180 [cifs]

[Kernel-packages] [Bug 1683341] Re: gstreamer-plugins-ugly-i386 dependency error

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  gstreamer-plugins-ugly-i386 dependency error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Attempting to install this gives the following:

  The following packages have unmet dependencies:

  gstreamer1.0-plugins-ugly:i386: Depends: gstreamer1.0-plugins-ugly-amr (= 
1.8.3-1ubuntu1) but 1.8.3-1ubuntu1 is to be installed
  Depends: libc6 (>= 2.7) but 2.24-3ubuntu2 is 
to be installed
  Depends: libdvdread4 (>= 4.1.3) but 5.0.3-1 
is to be installed
  Depends: libgcc1 (>= 1:3.0) but 
1:6.2.0-5ubuntu12 is to be installed
  Depends: libglib2.0-0 (>= 2.40) but 
2.50.2-2ubuntu1 is to be installed
  Depends: liborc-0.4-0 (>= 1:0.4.25) but 
1:0.4.26-1 is to be installed
  Depends: libstdc++6 (>= 5) but 
6.2.0-5ubuntu12 is to be installed

  
  The libc6 dependency is wrong, I would guess this should be 2.17 not 2.7 
which doesn't exist.

  cat version.log
  Ubuntu 4.8.0-46.49-generic 4.8.17
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   4535 F pulseaudio
   /dev/snd/controlC3:  mark   4535 F pulseaudio
   /dev/snd/controlC2:  mark   4535 F pulseaudio
   /dev/snd/controlC0:  mark   4535 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=3e34a9fd-33a3-4027-86ff-5151122c5379
  InstallationDate: Installed on 2010-03-14 (2590 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=bf8502af-6555-4b4c-a93f-11ee7121da7d ro quiet nosplash 
libata.force=noncq
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-46-generic N/A
   linux-backports-modules-4.8.0-46-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout floppy fuse libvirt libvirtd 
lpadmin netdev plugdev powerdev sambashare scanner tape video
  _MarkForUpload: True
  dmi.bios.date: 03/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A87TD/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TD/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1673333] Re: package linux-headers-4.8.0-42 4.8.0-42.45 failed to install/upgrade: unable to open '/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach-bf548/include/mach/defBF547

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  package linux-headers-4.8.0-42 4.8.0-42.45 failed to install/upgrade:
  unable to open '/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach-
  bf548/include/mach/defBF547.h.dpkg-new': Operation not permitted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This error occurred at the final stages of installing updates.
  I had run 
  sudo apt-get update
  followed by 
  sudo apt-get dist-upgrade

  This seems to happen in one form or another periodically.
  The fix is to run 
  sudo apt-get -f install
  until it doesn't fail. Sometimes once, in this case 5 or 6 times.
  Eventually, the install finished without errors, and then I restart, and 
everything tends to be ok.

  It seems that running it until it fixes the broken dependencies is
  just a normal part of updating?

  I've checked my drives for any signs of issues, and the smart utilities show 
no problems.
  If I'm doing something wrong, please let me know what it is, and I'll try and 
fix it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-headers-4.8.0-42 4.8.0-42.45
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jerry.lumpkins   4213 F pulseaudio
  Date: Thu Mar 16 01:24:16 2017
  DuplicateSignature:
   package:linux-headers-4.8.0-42:4.8.0-42.45
   Unpacking linux-image-extra-4.8.0-42-generic (4.8.0-42.45) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-rwCZmk/182-linux-image-extra-4.8.0-42-generic_4.8.0-42.45_amd64.deb
 (--unpack):
unable to open 
'/lib/modules/4.8.0-42-generic/kernel/drivers/staging/lustre/lustre/lmv/lmv.ko.dpkg-new':
 Operation not permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach-bf548/include/mach/defBF547.h.dpkg-new':
 Operation not permitted
  HibernationDevice: RESUME=UUID=4c1c5e08-0209-47f6-8250-d5e9218964b4
  InstallationDate: Installed on 2014-12-08 (829 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic 
root=UUID=58e4f4be-3dfc-4eaf-91b0-d70f9c1c7640 ro cgroup_enable=memory 
swapaccount=1 quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-4.8.0-42 4.8.0-42.45 failed to install/upgrade: 
unable to open 
'/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach-bf548/include/mach/defBF547.h.dpkg-new':
 Operation not permitted
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (144 days ago)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0502
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX PLUS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLXPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1671022] Re: package linux-headers-4.8.0-41 (not installed) failed to install/upgrade: nem sikerült megnyitni: „/usr/src/linux-headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dp

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  package linux-headers-4.8.0-41 (not installed) failed to
  install/upgrade: nem sikerült megnyitni: „/usr/src/linux-
  headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dpkg-new”: A művelet
  nem engedélyezett

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dpkg: Error processing archive: 
/var/cache/apt/archives/linux-headers-4.8.0-41_4.8.0-41.44_all.deb (--unpack):
   Can not open: 
„/usr/src/linux-headers-4.8.0-41/arch/powerpc/include/asm/floppy.h.dpkg-new”: 
Not permitted
  Errors while processing:
   /var/cache/apt/archives/linux-headers-4.8.0-41_4.8.0-41.44_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Nothing special, just unattended upgrades;

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-headers-4.8.0-41 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2172 F pulseaudio
tgortva5919 F pulseaudio
   /dev/snd/controlC0:  gdm2172 F pulseaudio
tgortva5919 F pulseaudio
  Date: Wed Mar  8 08:32:41 2017
  ErrorMessage: nem sikerült megnyitni: 
„/usr/src/linux-headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dpkg-new”: A 
művelet nem engedélyezett
  HibernationDevice: RESUME=UUID=d44cff4f-ea6a-47d6-9dc6-270d36dc20f8
  InstallationDate: Installed on 2017-03-02 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.8.0-41 (not installed) failed to 
install/upgrade: nem sikerült megnyitni: 
„/usr/src/linux-headers-4.8.0-41/arch/cris/boot/rescue/Makefile.dpkg-new”: A 
művelet nem engedélyezett
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1665589] Re: Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS Mobile Mouse 3600

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

** Changed in: bluez (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  Killer 1535 802.11 2×2 Wi-Fi + BT 4.1 controller can't discover MS
  Mobile Mouse 3600

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I saw number of posts here about Mobile Mouse 3600 but sadly none of
  them helped me to debug the issue.

  I have Killer 1535 card on my Dell XPS 13. According to specs it's
  Bluetooth 4.1 device. Mobile Mouse 3600 is Bluetooth Low Energy device
  of version 4.0.

  In theory these two devices should be able to communicate.
  Unfortunately they don't :(

  I'm on Ubuntu MATE 16.10 but I also tested it on Linux Mint 18 and
  Element OS. I have bluez 5.41 installed.

  Here is what info I have abut my devices

  usb-devices | awk '/e301/' RS=

  T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#=  4 Spd=12  MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0cf3 ProdID=e301 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  
  hciconfig -a | grep HCI

  HCI Version: 4.1 (0x7)  Revision: 0x0

  lsusb | grep Ath

  Bus 001 Device 004: ID 0cf3:e301 Atheros Communications, Inc.

  `sudo hcitool lescan` finds nothing.

  After clean installation `dmesg | grep ath10` gives

  [   14.979939] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [   14.981966] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
  [   15.263691] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/pre-cal-pci-:3a:00.0.bin failed with error -2
  [   15.263709] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/cal-pci-:3a:00.0.bin failed with error -2
  [   15.263734] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [   15.263736] ath10k_pci :3a:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [   15.440154] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [   15.440156] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 
1 dfs 0 testmode 0
  [   15.440582] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  [   15.532098] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
  [   17.658135] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
  [   17.770412] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0

  My WiFi works. I can also pair Bluetooth keyboard. Since I don't
  really know how device drivers work in Linux I noticed line with error
  about `firmware-5.bin` in output of dmesg. So I took missing file from
  https://github.com/kvalo/ath10k-
  firmware/tree/master/QCA6174/hw3.0/4.4. It turned out to be bad idea
  because it botched wifi/bluetooth completely. Here is what I had in
  log

  [3.519354] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [3.521259] ath10k_pci :3a:00.0: pci irq msi-x interrupts 8 
irq_mode 0 reset_mode 0
  [3.765880] ath10k_pci :3a:00.0: Direct firmware load for 
ath10k/cal-pci-:3a:00.0.bin failed with error -2
  [3.831220] ath10k_pci :3a:00.0: failed to fetch board data for 
ath10k/QCA6174/hw3.0 from bus=pci,bmi-chip-id=0,bmi-board-id=0/board-2.bin
  [5.887772] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [5.887786] ath10k_pci :3a:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff bmi 0:0) fw WLAN.RM.4.4-00022-QCARMSWPZ-2 fwapi 5 bdapi 1 htt-ver 
3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features 
wowlan,ignore-otp
  [5.887789] ath10k_pci :3a:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.884160] ath10k_pci :3a:00.0: could not suspend target (-11)
  [8.966789] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0
  [   11.178547] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [   14.176459] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11
  [   20.176417] ath10k_pci :3a:00.0: could not suspend target (-11)
  [   22.435758] ath10k_pci :3a:00.0: Unknown eventid: 90118
  [   25.432569] ath10k_pci :3a:00.0: failed to enable dynamic BW: -11

[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

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

** Also affects: makedumpfile (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883899
   Importance: Unknown
   Status: Unknown

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

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

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

** Changed in: kexec-tools (Ubuntu Artful)
   Status: New => Fix Released

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  In Progress
Status in makedumpfile package in Debian:
  Unknown

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch,

[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

** Also affects: kexec-tools (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

** Changed in: kexec-tools (Ubuntu Yakkety)
   Status: In Progress => Won't Fix

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  In Progress
Status in makedumpfile package in Debian:
  Unknown

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.

  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.

[Kernel-packages] [Bug 1752742] [NEW] Kernel deadlock when using cachefiles.

2018-03-01 Thread Daniel Ribeiro

Public bug reported:

Was using both a cifs share and a nfs share at the moment of the crash,
both network filesystems get mounted by automount, seems that the bug
happened at the cifs automatic umount. Machine froze and stopped
responding pings from the network, not even sysrq keys worked, needed a
hard power off. Kernel panic (at least what made to syslog) follows:

Mar  1 19:34:04 xps kernel: [ 5497.617469] [ cut here ]
Mar  1 19:34:04 xps kernel: [ 5497.617472] kernel BUG at 
/build/linux-fQ94TU/linux-4.4.0/fs/fscache/cookie.c:639!
Mar  1 19:34:04 xps kernel: [ 5497.617474] invalid opcode:  [#1] SMP 
Mar  1 19:34:04 xps kernel: [ 5497.617475] Modules linked in: rpcsec_gss_krb5 
nfsv4 nfs drbg ansi_cprng md4 nls_utf8 cifs ccm bnep pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(
OE) dm_cache_smq dm_cache dm_persistent_data dm_bio_prison zram dm_bufio 
lz4_compress libcrc32c uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 ath3k videobuf2_core btusb v4l2_com
mon btrtl videodev btbcm btintel snd_usb_audio joydev media input_leds 
bluetooth snd_usbmidi_lib snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_hd
a_codec_realtek snd_hda_codec_generic kvm dcdbas irqbypass snd_hda_intel arc4 
crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel ath9k 
aesni_intel snd_hda_core aes_x86_64 lrw sn
d_hwdep gf128mul glue_helper snd_pcm ath9k_common ablk_helper ath9k_hw cryptd 
snd_seq_midi ath snd_seq_midi_event snd_rawmidi nvidia_uvm(POE) mac80211 
snd_seq snd_seq_device snd_timer cfg802
11 serio_raw snd mei_me mei soundcore lpc_ich shpchp mac_hid binfmt_misc 
cachefiles nfsd fscache auth_rpcgss parport_pc nfs_acl lockd ppdev lp grace 
sunrpc parport autofs4 btrfs xor uas usb_
storage raid6_pq hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse 
fb_sys_fops ahci r8169 drm libahci mii video 
fjes
Mar  1 19:34:04 xps kernel: [ 5497.617515] CPU: 2 PID: 20454 Comm: umount 
Tainted: P   OE   4.4.0-116-generic #140-Ubuntu
Mar  1 19:34:04 xps kernel: [ 5497.617516] Hardware name: Dell Inc. XPS 
8700/0KWVT8, BIOS A08 04/16/2014
Mar  1 19:34:04 xps kernel: [ 5497.617517] task: 88034802c600 ti: 
88029858c000 task.ti: 88029858c000
Mar  1 19:34:04 xps kernel: [ 5497.617518] RIP: 0010:[]  
[] __fscache_cookie_put+0x3a/0x40 [fscache]
Mar  1 19:34:04 xps kernel: [ 5497.617525] RSP: 0018:88029858fd98  EFLAGS: 
00010282
Mar  1 19:34:04 xps kernel: [ 5497.617526] RAX: 0001 RBX: 
8802e00244d0 RCX: 0034
Mar  1 19:34:04 xps kernel: [ 5497.617527] RDX: 0001 RSI: 
8802e0024528 RDI: 8802e0024528
Mar  1 19:34:04 xps kernel: [ 5497.617528] RBP: 88029858fda0 R08: 
88041ec972c0 R09: 0001
Mar  1 19:34:04 xps kernel: [ 5497.617528] R10: 0010 R11: 
 R12: 8802dde8f000
Mar  1 19:34:04 xps kernel: [ 5497.617529] R13: 1f39 R14: 
 R15: 88034802cca0
Mar  1 19:34:04 xps kernel: [ 5497.617531] FS:  7f93632b5840() 
GS:88041ec8() knlGS:
Mar  1 19:34:04 xps kernel: [ 5497.617532] CS:  0010 DS:  ES:  CR0: 
80050033
Mar  1 19:34:04 xps kernel: [ 5497.617533] CR2: 2205d5e14000 CR3: 
000293ff6000 CR4: 00160670
Mar  1 19:34:04 xps kernel: [ 5497.617534] Stack:
Mar  1 19:34:04 xps kernel: [ 5497.617535]  8802e0024528 88029858fdb8 
c10a6517 880348d55800
Mar  1 19:34:04 xps kernel: [ 5497.617536]  88029858fdd0 c1854232 
880348d55800 88029858fdf8
Mar  1 19:34:04 xps kernel: [ 5497.617538]  c182d3e0 8800a1c7ce40 
880348d55000 880348d55008
Mar  1 19:34:04 xps kernel: [ 5497.617548] Call Trace:
Mar  1 19:34:04 xps kernel: [ 5497.617552]  [] 
__fscache_relinquish_cookie+0x87/0x120 [fscache]
Mar  1 19:34:04 xps kernel: [ 5497.617572]  [] 
cifs_fscache_release_super_cookie+0x32/0x90 [cifs]
Mar  1 19:34:04 xps kernel: [ 5497.617580]  [] 
cifs_put_tcon+0x100/0x180 [cifs]
Mar  1 19:34:04 xps kernel: [ 5497.617587]  [] 
cifs_put_tlink+0x47/0x60 [cifs]
Mar  1 19:34:04 xps kernel: [ 5497.617595]  [] 
cifs_umount+0x5b/0xc0 [cifs]
Mar  1 19:34:04 xps kernel: [ 5497.617602]  [] 
cifs_kill_sb+0x1e/0x30 [cifs]
Mar  1 19:34:04 xps kernel: [ 5497.617605]  [] 
deactivate_locked_super+0x48/0x80
Mar  1 19:34:04 xps kernel: [ 5497.617607]  [] 
deactivate_super+0x5c/0x60
Mar  1 19:34:04 xps kernel: [ 5497.617609]  [] 
cleanup_mnt+0x3f/0x90
Mar  1 19:34:04 xps kernel: [ 5497.617611]  [] 
__cleanup_mnt+0x12/0x20
Mar  1 19:34:04 xps kernel: [ 5497.617613]  [] 
task_work_run+0x86/0xb0
Mar  1 19:34:04 xps kernel: [ 5497.617616]  [] 
exit_to_usermode_loop+0xc2/0xd0
Mar  1 19:34:04 xps kernel: [ 5497.617618]  [] 
syscall_return_slowpath+0x4e/0x60
Mar  1 19:34:04 xps kernel: [ 5497.617621]  [] 
int_ret_from_sys_call+0x25/0x9f
Mar  1 19:34:04

[Kernel-packages] [Bug 1668062] Re: Black screen after waking from suspend, need to reboot to use the PC

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  Black screen after waking from suspend, need to reboot to use the PC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I installed a fresh Ubuntu 16.10.
  When I try to wake the system from suspend, I only get a black screen.
  The LCD back-light gets light up, the mouse pointer shows up, and it can be 
moved, but then I do not get anything else on the screen.

  I can still use Ctrl+Alt+F1 to switch to text screen.
  Switching  back with Alt+F7 leads back to the black screen.

  This makes it impossible to use Ubuntu 16.10, please address.
  I use Fedora 25 now, and does not suffer the same issue.

  I am happy to provide more details (hardware, logs), please let me
  know.

  Best regards,
  Marton
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D7p:   csalad22310 F...m pulseaudio
   /dev/snd/controlC1:  csalad22310 F pulseaudio
   /dev/snd/controlC0:  csalad22310 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0d7c78b5-bcee-4f78-ac98-35861e943e69
  InstallationDate: Installed on 2017-02-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic 
root=UUID=080d6932-790b-4bd2-84a7-c81995d324cc ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-39-generic N/A
   linux-backports-modules-4.8.0-39-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  Tags:  yakkety
  Uname: Linux 4.8.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2507
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A75-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2507:bd01/29/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1669532] Re: package linux-image-extra-4.8.0-40-generic 4.8.0-40.43 failed to install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-image-extra-4.8.0-40-generic.list-new« kann n

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  package linux-image-extra-4.8.0-40-generic 4.8.0-40.43 failed to
  install/upgrade: Neue Datei »/var/lib/dpkg/info/linux-image-
  extra-4.8.0-40-generic.list-new« kann nicht angelegt werden: Vorgang
  nicht zulässig

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  automated report, i got no clue what happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-extra-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  roman  2784 F pulseaudio
   /dev/snd/controlC1:  roman  2784 F pulseaudio
   /dev/snd/controlC0:  roman  2784 F pulseaudio
  Date: Thu Mar  2 16:43:13 2017
  ErrorMessage: Neue Datei 
»/var/lib/dpkg/info/linux-image-extra-4.8.0-40-generic.list-new« kann nicht 
angelegt werden: Vorgang nicht zulässig
  HibernationDevice: RESUME=UUID=65743a1a-1279-417e-ab26-cd17b1baa629
  InstallationDate: Installed on 2017-01-29 (31 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-40-generic 
root=UUID=3d889fca-fb58-4d48-bfb6-61c9d6408e49 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.8.0-40-generic 4.8.0-40.43 failed to 
install/upgrade: Neue Datei 
»/var/lib/dpkg/info/linux-image-extra-4.8.0-40-generic.list-new« kann nicht 
angelegt werden: Vorgang nicht zulässig
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1688470] Re: package linux-image-4.8.0-52-generic 4.8.0-52.55 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  package linux-image-4.8.0-52-generic 4.8.0-52.55 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  run-parts: executing /etc/kernel/postinst.d/dkms 4.8.0-52-generic 
/boot/vmlinuz-4.8.0-52-generic
  did not progress, it used no system resources and just hang.
  I had this problem before with nearly every kernel update in the past.

  I have to reboot, use the recovery mode, uninstall nvidia-drivers and
  then the update of the kernel works. After that I can reinstall nvidia
  graphics drivers.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2886 F pulseaudio
dirk   3286 F pulseaudio
   /dev/snd/controlC1:  gdm2886 F pulseaudio
dirk   3286 F pulseaudio
  Date: Fri May  5 08:51:43 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=016cefa8-4e13-45c6-a877-ddbc86b78741
  InstallationDate: Installed on 2017-01-15 (109 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: LENOVO 80NV
  ProcFB:
   0 inteldrmfb
   1 evdidrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic 
root=UUID=7ebecb7d-79da-41a5-84bd-68400bda8190 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11.2
  SourcePackage: linux
  Title: package linux-image-4.8.0-52-generic 4.8.0-52.55 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN27WW:bd11/12/2015:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK:
  dmi.product.name: 80NV
  dmi.product.version: Lenovo ideapad Y700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1692265] Re: package linux-image-4.8.0-46-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  package linux-image-4.8.0-46-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Here is an update . Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-46-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-22-generic.
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laguna 1233 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with CS4299 at irq 10'
 Mixer name : 'Cirrus Logic CS4299 rev 4'
 Components : 'AC97a:43525934'
 Controls  : 37
 Simple ctrls  : 22
  Date: Sat May 20 17:10:26 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=b23d1ed1-16c5-4627-a27b-ed406bbe27f9
  InstallationDate: Installed on 2017-01-27 (113 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer TravelMate C300
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=abb37240-7e72-475d-9608-03d7666d948a ro acpi=off quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.8.0-46-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/04
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.08
  dmi.board.name: TravelMate C300
  dmi.board.vendor: Acer
  dmi.board.version: Rev.A
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.08:bd07/09/04:svnAcer:pnTravelMateC300:pvr-1:rvnAcer:rnTravelMateC300:rvrRev.A:cvnAcer:ct1:cvrN/A:
  dmi.product.name: TravelMate C300
  dmi.product.version: -1
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1691161] Re: package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

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

Title:
  package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  Not Provided

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-signed-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue May 16 12:03:34 2017
  DuplicateSignature:
   package:linux-signed-image-4.8.0-52-generic:4.8.0-52.55
   Setting up linux-signed-image-4.8.0-52-generic (4.8.0-52.55) ...
   cp: error writing '/boot/vmlinuz-4.8.0-52-generic.efi.signed': No space left 
on device
   dpkg: error processing package linux-signed-image-4.8.0-52-generic 
(--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-18 (86 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: linux-signed
  Title: package linux-signed-image-4.8.0-52-generic 4.8.0-52.55 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1696463] Re: at update

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

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

Title:
  at update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  it ocured when mi toke the last version of lowlatency kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-53-lowlatency 4.8.0-53.56
  ProcVersionSignature: Ubuntu 4.8.0-53.56-lowlatency 4.8.17
  Uname: Linux 4.8.0-53-lowlatency i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kim1898 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jun  7 12:13:18 2017
  HibernationDevice: RESUME=UUID=01af17d0-cd9e-4d01-9cd9-28cd3358eff2
  InstallationDate: Installed on 2016-10-21 (229 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R430/R480/R440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-53-lowlatency 
root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-lowlatency N/A
   linux-backports-modules-4.8.0-53-lowlatency  N/A
   linux-firmware   1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-06-03 (4 days ago)
  dmi.bios.date: 05/25/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 05UZ.M013.20100525.XW
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: R430/R480/R440
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr05UZ.M013.20100525.XW:bd05/25/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR430/R480/R440:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR430/R480/R440:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: R430/R480/R440
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1696582] Re: package linux-image-4.8.0-54-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

Marking as Invalid because the release is EOL is not correct. Marking as 
Incomplete. Also, 18.04 is (at the time of writing) still in development, and 
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10?

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

Title:
  package linux-image-4.8.0-54-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problemas sérios para abrir os aplicativos, principalmente o ubuntu
  store.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-54-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  patricmmenezes   3924 F pulseaudio
   /dev/snd/controlC0:  patricmmenezes   3924 F pulseaudio
  Date: Wed Jun  7 18:19:11 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=ea7984c1-307a-4b16-88fb-16ee3c9c155f
  InstallationDate: Installed on 2017-04-27 (41 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 3437
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic.efi.signed 
root=UUID=378296e0-4da7-408b-b80b-ebd59144c548 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.8.0-54-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to yakkety on 2017-04-28 (40 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 02TT83
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn02TT83:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1730599] Re: [Bug] [USB Function][CFL-CNL PCH]Stall Error and USB Transaction Error in trace, Disable of device-initiated U1/U2 failed and rebind failed: -517 during suspend/res

2018-03-01 Thread Thadeu Lima de Souza Cascardo

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

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

Title:
  [Bug] [USB Function][CFL-CNL PCH]Stall Error and USB Transaction Error
  in trace, Disable of device-initiated U1/U2 failed and rebind failed:
  -517 during suspend/resume with usb storage.

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Description:
  Hardware Configuration
  Board ID  :CoffeeLake S UDIMM RVP
  PCH: CNL, PCH-H
  BIOS: CNLSFWR1.R00.X088.D51.1706060006
  KSC FW1.00
  Steps;
  1.connect usb keyboard and usb mass storage to usb host.
  2.let system enter s4 and resume
  [Expected Results]
  There is no error and fail in dmesg and trace.
  [Observed Results]
  There is some error and fail in dmesg and trace.

  Target Kernel: 4.16
  Target Release: 18.04

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-03-01 Thread Tetsuo Handa

Since 18.04 seems to give up LSM stacking patchset, safest choice (if
acceptable) would be to completely revert LSM stacking patchset for
17.10 as well.

-- 
You 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:
  In Progress

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:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-;

[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic

2018-03-01 Thread Seth Forshee

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  Missing firmware in linux-image-4.15.0-10-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  linux-image-4.15.0-10-generic doesn't have the firmware that linux-
  image-4.13.0-32-generic has. It doesn't have any of the files that are
  present in 4.13 in /lib/firmware/4.13.0-32-generic/.

  For me, this means i can boot 4.15, but my network wont work because
  of:

  kernel: [   13.468996] bnx2 :0b:00.0: Direct firmware load for 
bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
  kernel: [   13.468998] bnx2: Can't load firmware file 
"bnx2/bnx2-mips-09-6.2.1b.fw"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 feb 23 13:12 seq
   crw-rw 1 root audio 116, 33 feb 23 13:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  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:
  Date: Fri Feb 23 13:50:38 2018
  InstallationDate: Installed on 2018-02-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM System x3550 M3 -[7944S77]-
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E158AUS-1.16]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: System x3550 M3 -[7944S77]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

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

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

[Kernel-packages] [Bug 1752621] Re: BUG: unable to handle kernel paging request at ffffded5330000a0

2018-03-01 Thread Tetsuo Handa

Thanks for reporting. This is a duplicate of bug 1734327 .

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

Title:
  BUG: unable to handle kernel paging request at ded533a0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [  155.111268] BUG: unable to handle kernel paging request at ded533a0
  [  155.111335] IP: kfree+0x53/0x160
  [  155.111357] PGD 0 
  [  155.111358] P4D 0 

  [  155.111401] Oops:  [#1] SMP PTI
  [  155.111424] Modules linked in: gpio_ich intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass 
snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc aesni_intel snd_hwdep aes_x86_64 crypto_simd snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi joydev input_leds glue_helper snd_seq 
snd_seq_device cryptd snd_timer intel_cstate intel_rapl_perf mei_me shpchp snd 
mei soundcore lpc_ich mac_hid serio_raw parport_pc ppdev lp parport ip_tables 
x_tables autofs4 hid_generic usbhid hid i915 video i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt ahci fb_sys_fops r8169 libahci drm mii
  [  155.111809] CPU: 0 PID: 1587 Comm: postgres Not tainted 4.13.0-36-generic 
#40-Ubuntu
  [  155.111853] Hardware name: Gigabyte Technology Co., Ltd. 
H67A-USB3-B3/H67A-USB3-B3, BIOS F7 03/27/2012
  [  155.111906] task: 8e971b4845c0 task.stack: 9c1bc2e7c000
  [  155.111942] RIP: 0010:kfree+0x53/0x160
  [  155.111966] RSP: 0018:9c1bc2e7fce8 EFLAGS: 00010282
  [  155.111998] RAX:  RBX: 00102aa3 RCX: 
0003
  [  155.112039] RDX: 2d8460201cf0 RSI: 00010080 RDI: 
716c4000
  [  155.112080] RBP: 9c1bc2e7fd00 R08: 00025d80 R09: 
bafc6a19
  [  155.112121] R10: ded53380 R11:  R12: 
8e974abe7800
  [  155.112162] R13: baba74d4 R14:  R15: 
8e9714f4d3c0
  [  155.112204] FS:  () GS:8e975fa0() 
knlGS:
  [  155.112250] CS:  0010 DS:  ES:  CR0: 80050033
  [  155.112285] CR2: ded533a0 CR3: 00022c20a001 CR4: 
000606f0
  [  155.112326] Call Trace:
  [  155.112349]  security_sk_free+0x44/0x60
  [  155.112377]  __sk_destruct+0x10b/0x190
  [  155.112403]  sk_destruct+0x20/0x30
  [  155.112427]  __sk_free+0x82/0xa0
  [  155.112451]  sk_free+0x19/0x20
  [  155.112472]  tcp_close+0x238/0x3f0
  [  155.112498]  inet_release+0x42/0x70
  [  155.112522]  sock_release+0x25/0x80
  [  155.112546]  sock_close+0x12/0x20
  [  155.114960]  __fput+0xea/0x230
  [  155.117332]  fput+0xe/0x10
  [  155.119604]  task_work_run+0x7c/0xa0
  [  155.121861]  do_exit+0x2d2/0xae0
  [  155.124100]  ? entry_SYSCALL_64_after_hwframe+0xd4/0x139
  [  155.126330]  ? entry_SYSCALL_64_after_hwframe+0xc6/0x139
  [  155.128524]  ? entry_SYSCALL_64_after_hwframe+0xbf/0x139
  [  155.130674]  ? entry_SYSCALL_64_after_hwframe+0xb8/0x139
  [  155.132757]  ? entry_SYSCALL_64_after_hwframe+0xb1/0x139
  [  155.134769]  do_group_exit+0x43/0xb0
  [  155.136307]  SyS_exit_group+0x14/0x20
  [  155.138219]  entry_SYSCALL_64_fastpath+0x24/0xab
  [  155.140110] RIP: 0033:0x7fe7b4851fd8
  [  155.141984] RSP: 002b:7ffe7f1d1e88 EFLAGS: 0246 ORIG_RAX: 
00e7
  [  155.143882] RAX: ffda RBX: 563529f04030 RCX: 
7fe7b4851fd8
  [  155.145590] RDX:  RSI: 003c RDI: 

  [  155.147316] RBP: 7ffe7f1d1e80 R08: 00e7 R09: 
fef8
  [  155.148956] R10: 7fe7acf95148 R11: 0246 R12: 
7fe7acf94d90
  [  155.150230] R13: 0036 R14:  R15: 
7ffe7f1d1c10
  [  155.151492] Code: 00 80 49 01 da 0f 82 1f 01 00 00 48 c7 c7 00 00 00 80 48 
2b 3d 4f b2 01 01 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 2d b2 01 01 <49> 8b 
42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 
  [  155.152892] RIP: kfree+0x53/0x160 RSP: 9c1bc2e7fce8
  [  155.154283] CR2: ded533a0
  [  155.167949] ---[ end trace 28ca6dd18121abd3 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1058 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  1 20:51:56 2018
  HibernationDevice: RESUME=UUID=dcaa0aaf-ec9b-4eec-962b-498d547772f5
  InstallationDate: Installed on 2018-02-23 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless

[Kernel-packages] [Bug 1752044] Re: Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio Emissions Directive)

2018-03-01 Thread Seth Forshee

These commits have been picked up when rebasing on upstream.

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio
  Emissions Directive)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  To comply with CE-RED (Radio Emissions Directive),
  ath10k/QCA6174/hw3.0/board-2.bin and
  ath10k/QCA6174/hw3.0/firmware-6.bin have to be updated.

  The commits are:

  commit 1d1dd4be21cde408b0fb12774d477293bc8d4cc2
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update board-2.bin
  
  Signed-off-by: Kalle Valo 

  commit 6f1d3b7cfeef426f3c3d79bf916e3bef8f82a3dc
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1
  
  Signed-off-by: Kalle Valo 

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

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

2018-03-01 Thread Scott Emmons

I found the xenial issue I was thinking of [1] but I'd be surprised if
that particular case regressed (it had to do with use of /etc/mtab). For
completeness, I'll mention it here anyway.

[1] https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1607920

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

2018-03-01 Thread Scott Emmons

Note that for bionic as of this week the behavior is now different. This
particular problem doesn't surface for zfs-import-cache.service (because
the ConditionPathExists expression is back in the unit).

It's not all good news, however, as that one failed unit has been
replaced with:

$ systemctl --failed
  UNIT  LOAD   ACTIVE SUBDESCRIPTION
● zfs-mount.service loaded failed failed Mount ZFS filesystems
● zfs-share.service loaded failed failed ZFS file system shares
● zfs-zed.service   loaded failed failed ZFS Event Daemon (zed)

All because the zfs kernel module is now no longer being loaded. So,
it's related to this bug in that the zfs-import-cache.service was
loading the zfs kernel module because it was running unconditionally.
Now that this unit is no longer running do to ConditionPathExists, other
zfs units fail now.

I'm fairly certain we ran into this same issue back in xenial, I'll see
if I can track down the launchpad # for it. Thanks!

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

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

2018-03-01 Thread Brad Figg

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

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Fix Released

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

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Fix Released

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

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

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


  
  

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

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

  ---uname output---
  na

  Machine Type = na

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

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

  Userspace tool common name: makedumpfile

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

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

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

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

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2018-03-01 Thread Scott Moser

Joseph forwarded this upstream.  LKML mailing list post
https://lkml.org/lkml/2018/3/1/812 .

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  In Progress

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
    Installed: 4.13.0-16.19
    Candidate: 4.13.0-16.19
    Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  It appears that since the initramfs loads the bcache module which
  probes and finds all of the cache devices and backing devices then
  once the rootfs is mounted and udev gets to run, the bcache kernel
  module does not emit the CACHED_UUID value into the environment if the
  underlying devices are already registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
    register_bdev()
  bch_cached_dev_run()
    kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes:
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  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 Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A

[Kernel-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

2018-03-01 Thread Etienne URBAH

With bluez version 5.46-0ubuntu3 from Ubuntu 17.10 (Artful), the issue
is still there :

The command 'bluetoothctl' systematically hangs.


** Tags added: artful

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

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

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

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

[Kernel-packages] [Bug 1738263] Re: Touchpad not working and locking CPU

2018-03-01 Thread Luke Williams

Hello,

I actually installed the patch on my laptop with the latest Artful
kernel and I did not see any difference in the performance of the
touchpad on the laptop. It could be that it is because the patch is for
a different version of the laptop (G752VS) which while similar, it does
have a different PCI address for the touchpad, which I think is why it
didn't work.

Unfortunately, I'm not sure how to come up with the settings that would
work with our Touchpad, so I currently have it disabled in Gnome and use
a regular mouse for moving and it works for now. Kind of a pain that I
have to use that as a work around but its either that, or deal with a
touchpad that performs so bad that I would rather work in the terminal
all day and not get anything done.

I noticed that by moving to the 4.13 kernel, even in Xenial, a lot of devices 
work better, and installing the proprietary NVidia drivers fixes a lockup issue 
and the F1-F7 buttons now work so I can break into a TTY session where using 
the nouveau drivers just led to CPU hangs (never the same CPU either, even 
though CPU2 was very common and happened more than the others, I saw 1 and 3 
also hang but I also noticed with 4.13 kernel compared to the 4.4 kernel that 
they included skylake extensions which fixed a lot of issues I was running into 
for performance and just the system randomly hanging. I also couldn't install 
Ubuntu without passing the nouveau.modeset=0 kernel parameter in the grub menu 
since it would kernel panic during boot saying CPU's were frozen and the 
nouveau driver was failing to start properly. 
The laptop would install clean and you run on the nouveau drivers once 
installed and running, but if you tried any of the F1-F7 keys nothing would 
happen and when you tried to reboot or shutdown, it would just hang and never 
power off the laptop. Also audio wouldn't work. Ubuntu would detect it and said 
that there is a sound card installed, but if you tried to play music, nothing, 
volume control would say it was going up and down, but no audio. Once I 
installed the NVidia Proprietary drivers the system started working as normal, 
with exception of the touchpad. 
It is a version 4 touchpad. I read about it features from kernel.org [1] and 
that helped me deduce what version, and according to kernel.org it is supported 
and should work OOB. What weird that I noticed is that before I login to Gnome 
desktop, the mouse seems to perform much better, and the scrolling feature 
works like a champ, it is just the regular mouse movement and touch to click 
which feels like it is almost over sensitive to that. I will move the mouse 
from the center of the screen to the sidebar to Firefox, which requires about 6 
full, edge to edge trackpad drags, and in those drags, it will try to select 
and hightlight whatever is on my desktop at that time, and only move about 1 
inch at a time, not at all, or fly way past what I'm trying to get to and I 
have to retry.
As Zibri mentioned, the mouse functions properly in Windows 10 and even in the 
BIOS. I haven't tried it on any other Distro's yet. That is my next step to 
maybe see if the xinput driver needs to use some other driver like mtrack or 
something more generic. I would think backwards compatibility would take hold 
here, but not so much.
I'm also wondering if perhaps it is not using correct registers which is why 
Zibri was seeing the processor load being high with the multitouch_hid.ko.
I did try a work around kernel parameter of i8042.reset which does make the 
touchpad work a little better, but as time progresses, you will notice that the 
touchpad responsiveness gets worse and sensitivity starts to get overly active 
over time. I have not tried the i8042.nomux=1 yet to as well as adjusting the 
CRC for the i8042 interface as seen on [2].
I have also, just for testing adjusted the scroll speed and disabled touch to 
click since the touchpad is a large button anyways might as well not worry 
about inadvertent clicks while trying to move the mouse with the touchpad.
I noticed as well the Kai-Heng mentioned that the patch is not correct 
according to ELAN, and that a firmware update "should" fix the issue. I've been 
to Asus's site, as well as ELAN's site to find an update with no joy. If ELAN 
says a firmware fix will fix this issue, they should at least release it. I 
would Run Windows setup USB i Have (dang kids need Windows for their games...) 
and install the firmware patch that way just like I did for the BIOS patch that 
came out November 3, 2017 (which didn't really do anything since I was running 
302 and current patch as of March 1, 2018 is 304)

I did try the Bionic Daily build with the 4.15 kernel to see if that worked 
better and still no joy with that. I still had to pass the nouveau.modest=0 to 
get it to boot properly (Almost like the NVIDIA GeForce GTX 1050 Mobile is too 
new for the open source nouveau driver which is why proprietary drivers from 
NVidia work).
Once the system is

[Kernel-packages] [Bug 1685723] Re: [Feature] GLK/CNL:eMMC 5.1 support

2018-03-01 Thread pragyansri.pa...@intel.com

That is correct. This feature capability first introduced in Geminilake
(GLK). Same code capability is used in Coffelake and Cannonlake SKUs.

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

Title:
  [Feature] GLK/CNL:eMMC 5.1 support

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  CNL will have eMMC5.1 capable host controller that includes new features:
  1) Command queue support – making the data transfers highly efficient by 
offloading the software overhead into the controller.
  2) eMMC 5.1 further improves the reliability of operation by utilizing an 
“enhanced strobe” at the PHY layer.
  The eMMC5.1 is backward compatible with the existing eMMC 4.51 and eMMC 5.0 
Devices.

  Target Kernel:4.16

  Target Release: 18.04

  Target Platform: GLK/CNL

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

-- 
Mailing list: https://launchpad.net/~kernel-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 s...@us.ibm.com 2018-03-01 15:07 EDT---
(In reply to comment #29)
> (In reply to comment #28)
> > (In reply to comment #27)
> > > @paelzer yes, that is us agreeing with your plan
> >
> > Does it mean that we are not going to have HTM support on KVM guests, even
> > in POWER8?
>
> you would use the 2.10 machine type for that, right?
Right. This is about the new machine type.

-- 
You 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:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

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.

[Kernel-packages] [Bug 1752695] Re: hisi_sas: Add disk LED support

** Description changed:

  [Impact]
  The disk LED is not supported on HiSilicon D05 systems
  
  [Test Case]
+ View LED. (Not sure if this is a "online" LED or an "activity" LED yet)
  
  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

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

Title:
  hisi_sas: Add disk LED support

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

Bug description:
  [Impact]
  The disk LED is not supported on HiSilicon D05 systems

  [Test Case]
  View LED. (Not sure if this is a "online" LED or an "activity" LED yet)

  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

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

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

[Kernel-packages] [Bug 1685723] Re: [Feature] GLK/CNL:eMMC 5.1 support

2018-03-01 Thread Thadeu Lima de Souza Cascardo

Following commits are not on 4.15 and were successfully cherry-picked.
The changes are limited to mmc, but that impacts lots of hardware and
platforms.

4512bd370b111dd7ffc437ddd3179391df68fe1b mmc: block: No need to export 
mmc_cleanup_queue()
41e3efd07d5a02c80f503e29d755aa1bbb4245de mmc: block: Simplify cleaning up the 
queue
afab1bb8b40c61458e009fdc323c9740f95fcd5b mmc: core: Make mmc_pre_req() and 
mmc_post_req() available
6d3898a6a517d0effa1d1e337c03b16bafb6fc96 mmc: block: Add error-handling comments
c3d53d0da69d127f488dc85638e9440220b268e8 mmc: core: Add parameter use_blk_mq
81196976ed946cbf36bb41ddda402853c7df7cfa mmc: block: Add blk-mq support
1e8e55b67030c6a2fef893d428bdcd611f73705c mmc: block: Add CQE support
a4080225f51dcea129d26185a35acfbb3770a32d mmc: cqhci: support for command queue 
enabled host
8ee82bda230fc972c7ee3bb15ce1260eefb4721c mmc: sdhci-pci: Add CQHCI support for 
Intel GLK
10f21df4a23540b5da8e88d1030ff8c37818e04f mmc: block: blk-mq: Add support for 
direct completion
88a516461ee07a994c0e7016faf85f3466de1d09 mmc: block: blk-mq: Separate card 
polling from recovery
c89b4851c67fb7354862850ae181de883269487d mmc: block: Make card_busy_detect() 
accumulate all response error bits
f47a1fe346b1568df0e9b158574b2939432313df mmc: block: blk-mq: Check error bits 
and save the exception bit when polling card busy
7701885e56cee3de4447c0653f9059b62844983b mmc: block: Check the timeout 
correctly in card_busy_detect()
0987c6b046e199b9b922a585c62e9503486fe0bc mmc: block: Check for transfer state 
in card_busy_detect()
92c0a0cc9483c6b9cc1b61273d30a0a601cb5e15 mmc: block: Add timeout_clks when 
calculating timeout
6b7a363d2ce83e3940dc0c3628e478fe95f23985 mmc: block: Reduce polling timeout 
from 10 minutes to 10 seconds
7eb43d537166c7d767af450901acd0ecbf94625c mmc: block: blk-mq: Stop using legacy 
recovery
42f532da3a44843668dbacc1838a028b0a9b7373 mmc: mmc_test: Do not use 
mmc_start_areq() anymore
d2383318c5a626312d166217e3788e54b1650c56 mmc: core: Ensure cmd_completion is 
initialized
23a185254ace8e63dc4ca36e0315aed9440ae749 mmc: mmc_test: Ensure command queue is 
disabled for testing
1bec43a3b181baebdf8a4cd739b480a9132601d7 mmc: core: Remove option not to use 
blk-mq
0fbfd12518303e9b32ac9fd231439459eac848f9 mmc: block: Remove code no longer 
needed after the switch to blk-mq
126b62700386da782f83579e9b0431ea76c2da3d mmc: core: Remove code no longer 
needed after the switch to blk-mq
0562315b86372d2cdd9cc8924b92cfab37049fbc mmc: cqhci: Ensure macro parameters 
are wrapped in parentheses

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

Title:
  [Feature] GLK/CNL:eMMC 5.1 support

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  CNL will have eMMC5.1 capable host controller that includes new features:
  1) Command queue support – making the data transfers highly efficient by 
offloading the software overhead into the controller.
  2) eMMC 5.1 further improves the reliability of operation by utilizing an 
“enhanced strobe” at the PHY layer.
  The eMMC5.1 is backward compatible with the existing eMMC 4.51 and eMMC 5.0 
Devices.

  Target Kernel:4.16

  Target Release: 18.04

  Target Platform: GLK/CNL

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

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

[Kernel-packages] [Bug 1752695] Re: hisi_sas: Add disk LED support

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

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

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

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

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

Title:
  hisi_sas: Add disk LED support

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

Bug description:
  [Impact]
  The disk LED is not supported on HiSilicon D05 systems

  [Test Case]
  View LED. (Not sure if this is a "online" LED or an "activity" LED yet)

  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

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

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

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

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

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
  [  240.308340] Instruction dump:
  [  240.308400] 4bfff9f1 4bfffe50 3c4c00e6 384232a0 7c0802a6 6000 3921

[Kernel-packages] [Bug 1752236] Re: Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Title:
  Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

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

Bug description:
  == Comment: #0 - JENIFER HOPPER  - 2018-02-27 17:25:59 ==
  +++ This bug was initially created as a clone of Bug #165215 +++

  ---Problem Description---
  Paul Mackerras has posted a fix to a Radix page fault handler bug in KVM:

  http://patchwork.ozlabs.org/patch/877033/
  " KVM: PPC: Book3S HV: Fix handling of large pages in radix page fault 
handler "

  This is critical for P9 KVM performance. Using an open source database 
workload, we saw an 11% throughput improvement with this patch when the guest 
was backed w/ 2MB hugepages. Without this patch, hugepage backing does not help 
performance compared to base page size. 
   
  ---uname output---
  18.04 lts
   
  Machine Type = 5104-22C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
Back guest w/ 2MB pages, run a throughput test and compare performance.
   
  Contact Information = jhop...@us.ibm.com

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

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

[Kernel-packages] [Bug 1750568] Re: qeth: check not more than 16 SBALEs on the completion queue

2018-03-01 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  qeth: check not more than 16 SBALEs on the completion queue

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  af_iucv socket programs with HiperSockets as transport make use of the qdio 
completion queue.
  Running such an af_iucv socket program may result in a crash which can be 
seen 
  in bug comment #1.  This issue is fixed by mainline commit 903e48531e8b.

  Commit 903e48531e8b is in mailine as of 4.8-rc8, so it is only needed
  in Xenial.

  == Fix ==
  903e48531e8b ("qeth: check not more than 16 SBALEs on the completion queue")

  == Regression Potential ==
  Low. Limited to s390.

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

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

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

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

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

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

Title:
  hisi_sas: Add disk LED support

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

Bug description:
  [Impact]
  The disk LED is not supported on HiSilicon D05 systems

  [Test Case]

  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

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

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

[Kernel-packages] [Bug 1752695] [NEW] hisi_sas: Add disk LED support

Public bug reported:

[Impact]
The disk LED is not supported on HiSilicon D05 systems

[Test Case]

[Regression Risk]
Code only touches the hisi_sas driver, so risk is limited to platforms that use 
it (i.e. the D05)

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

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

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

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

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

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

Title:
  hisi_sas: Add disk LED support

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

Bug description:
  [Impact]
  The disk LED is not supported on HiSilicon D05 systems

  [Test Case]

  [Regression Risk]
  Code only touches the hisi_sas driver, so risk is limited to platforms that 
use it (i.e. the D05)

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

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

[Kernel-packages] [Bug 1750568] Re: qeth: check not more than 16 SBALEs on the completion queue

** Tags removed: bugnameltc-164867 severity-high

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

Title:
  qeth: check not more than 16 SBALEs on the completion queue

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  af_iucv socket programs with HiperSockets as transport make use of the qdio 
completion queue.
  Running such an af_iucv socket program may result in a crash which can be 
seen 
  in bug comment #1.  This issue is fixed by mainline commit 903e48531e8b.

  Commit 903e48531e8b is in mailine as of 4.8-rc8, so it is only needed
  in Xenial.

  == Fix ==
  903e48531e8b ("qeth: check not more than 16 SBALEs on the completion queue")

  == Regression Potential ==
  Low. Limited to s390.

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

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

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

[Kernel-packages] [Bug 1750568] Re: qeth: check not more than 16 SBALEs on the completion queue

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090521.html

** Description changed:

- Description: qeth: check not more than 16 SBALEs on the completion queue 
Symptom: Kernel crash Problem: af_iucv socket programs with HiperSockets as 
transport make use of the qdio completion queue.
- Running such an af_iucv socket program may result in a crash - see #1
+ == SRU Justification ==
+ af_iucv socket programs with HiperSockets as transport make use of the qdio 
completion queue.
+ Running such an af_iucv socket program may result in a crash which can be 
seen 
+ in bug comment #1.  This issue is fixed by mainline commit 903e48531e8b.
+ 
+ Commit 903e48531e8b is in mailine as of 4.8-rc8, so it is only needed in
+ Xenial.
+ 
+ == Fix ==
+ 903e48531e8b ("qeth: check not more than 16 SBALEs on the completion queue")
+ 
+ == Regression Potential ==
+ Low. Limited to s390.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.

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

Title:
  qeth: check not more than 16 SBALEs on the completion queue

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  af_iucv socket programs with HiperSockets as transport make use of the qdio 
completion queue.
  Running such an af_iucv socket program may result in a crash which can be 
seen 
  in bug comment #1.  This issue is fixed by mainline commit 903e48531e8b.

  Commit 903e48531e8b is in mailine as of 4.8-rc8, so it is only needed
  in Xenial.

  == Fix ==
  903e48531e8b ("qeth: check not more than 16 SBALEs on the completion queue")

  == Regression Potential ==
  Low. Limited to s390.

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

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

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

[Kernel-packages] [Bug 1750813] Re: qeth: fix L3 next-hop im xmit qeth hdr

2018-03-01 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  qeth: fix L3 next-hop im xmit qeth hdr

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  == SRU Justification ==
  The current code accesses rtable->rt_gateway without checking that rtable
  is a valid address. The accidental access to a lowcore area results in a
  random next-hop address in the qeth_hdr.  rtable (or more precisely,
  skb_dst(skb)) can be NULL in rare cases (for instance together with AF_PACKET 
sockets).

  The solution is to add the missing NULL-ptr checks, which is done by
  commit ec2c6726322f.

  Commit ec2c6726322f is in mainline as of v4.13-rc5, so this fix is
  only needed in Xenial.

  == Fix ==
  ec2c6726322f ("s390/qeth: fix L3 next-hop in xmit qeth hdr")

  == Regression Potential ==
  Low.  Limited to s390.

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


  
  Upstream Commit:
  ec2c6726322f0d270bab477e4904bf9496f70ee5
  kernel 4.13

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

-- 
Mailing list: https://launchpad.net/~kernel-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

I'm wondering if we want to see what type of feedback is first received
from upstream.

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

Title:
  Kernel panic on a nfsroot system

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

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:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0

[Kernel-packages] [Bug 1750813] Re: qeth: fix L3 next-hop im xmit qeth hdr

SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090520.html

** Description changed:

- Description:  qeth: fix L3 next-hop im xmit qeth hdr
+ == SRU Justification ==
+ The current code accesses rtable->rt_gateway without checking that rtable
+ is a valid address. The accidental access to a lowcore area results in a
+ random next-hop address in the qeth_hdr.  rtable (or more precisely,
+ skb_dst(skb)) can be NULL in rare cases (for instance together with AF_PACKET 
sockets).
  
- Symptom:  wrong destination address in qdio header
+ The solution is to add the missing NULL-ptr checks, which is done by
+ commit ec2c6726322f.
  
- Problem:  The current code accesses rtable->rt_gateway without checking
-   that rtable is a valid address. The accidental access to a
-   lowcore area results in a random next-hop address in the
-   qeth_hdr.
-   rtable (or more precisely, skb_dst(skb)) can be NULL in rare
-   cases (for instance together with AF_PACKET sockets).
+ Commit ec2c6726322f is in mainline as of v4.13-rc5, so this fix is only
+ needed in Xenial.
  
- Solution: Add the missing NULL-ptr checks.
- Reproduction: AF_PACKET program sending raw data
+ == Fix ==
+ ec2c6726322f ("s390/qeth: fix L3 next-hop in xmit qeth hdr")
+ 
+ == Regression Potential ==
+ Low.  Limited to s390.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
  
  
  Upstream Commit:
  ec2c6726322f0d270bab477e4904bf9496f70ee5
  kernel 4.13

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

Title:
  qeth: fix L3 next-hop im xmit qeth hdr

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  == SRU Justification ==
  The current code accesses rtable->rt_gateway without checking that rtable
  is a valid address. The accidental access to a lowcore area results in a
  random next-hop address in the qeth_hdr.  rtable (or more precisely,
  skb_dst(skb)) can be NULL in rare cases (for instance together with AF_PACKET 
sockets).

  The solution is to add the missing NULL-ptr checks, which is done by
  commit ec2c6726322f.

  Commit ec2c6726322f is in mainline as of v4.13-rc5, so this fix is
  only needed in Xenial.

  == Fix ==
  ec2c6726322f ("s390/qeth: fix L3 next-hop in xmit qeth hdr")

  == Regression Potential ==
  Low.  Limited to s390.

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


  
  Upstream Commit:
  ec2c6726322f0d270bab477e4904bf9496f70ee5
  kernel 4.13

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

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

[Kernel-packages] [Bug 1752680] Re: Night light does not work in some cases

2018-03-01 Thread Hrishikesh Barua

These log files collect private information like the contents of my
drives, which is not acceptable. I cannot run the apport-collect
command.

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

Title:
  Night light does not work in some cases

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-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.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1743856] Re: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode)

SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090516.html

** Description changed:

- The sb_edac needs additional patch to enable EDAC to know of the existence of
some DIMMs attached to channels while figuring out the size of the DIMMs and
the cluster mode is SNC2 or SNC4.
- All the thread connected with this issue is described here
https://www.spinics.net/lists/linux-edac/msg08170.html.
+ == SRU Justification ==
+ The sb_edac needs this patch to enable EDAC to know of the existence of
+ some DIMMs attached to channels while figuring out the size of the DIMMs
+ and the cluster mode is SNC2 or SNC4.
+
+ All the thread connected with this issue is described here
+ https://www.spinics.net/lists/linux-edac/msg08170.html.
+
+ Commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 is in mailine as of
+ v4.15-rc1.
+
+ == Fix ==
+ commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36
+ Author: Luis Felipe Sandoval Castro
+ Date: Thu Sep 28 08:54:42 2017 -0500
+
+ EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4
+ mode
+
+ == Regression Potential ==
+ Low. Limited to EDAC checking dimm capacity.
+
+ == 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.
+

Please backport the following patch:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=24281a2f4ca569d44e44e4cbc500cf08e7bb4c36
to solve the sb_edac driver issue on Ubuntu 17.10.

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

Title:
EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM
sysfs entries with KNL SNC2/SNC4 mode)

Status in intel:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
Fix Released

Bug description:
== SRU Justification ==
The sb_edac needs this patch to enable EDAC to know of the existence of
some DIMMs attached to channels while figuring out the size of the DIMMs
and the cluster mode is SNC2 or SNC4.

All the thread connected with this issue is described here
https://www.spinics.net/lists/linux-edac/msg08170.html.

Commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 is in mailine as of
v4.15-rc1.

== Fix ==
commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36
Author: Luis Felipe Sandoval Castro
Date: Thu Sep 28 08:54:42 2017 -0500

EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4
mode

== Regression Potential ==
Low. Limited to EDAC checking dimm capacity.

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

Please backport the following patch:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=24281a2f4ca569d44e44e4cbc500cf08e7bb4c36
to solve the sb_edac driver issue on Ubuntu 17.10.

Thank you!

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

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

[Kernel-packages] [Bug 1752672] cxlflash proposed patches to 4.17 upstream kernel

--- Comment on attachment From ukri...@us.ibm.com 2018-03-01 13:47 
EDT---


Attaching the proposed patches that have been sent to community.

** Attachment added: "cxlflash proposed patches to 4.17 upstream kernel"
   
https://bugs.launchpad.net/bugs/1752672/+attachment/5066336/+files/cxlflash_ocxl.tar.gz

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

Title:
  CAPI Flash (cxlflash) update

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

Bug description:
  This is a feature for capi flash (cxlflash) inside the kernel.

  We have upstreamed the below 38 patches but they are not in the
  maintainers tree yet. I anticipate them to be available by Friday this
  week. I dont want to miss the boat for 18.04 feature code cutoff. Can
  you please suggest if I should submit these patches as SAUCE patches
  or can it be pulled from mainstream once maintainer pulls it in ?

  8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts
  8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context 
control register value
  44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier 
names
  9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend
  0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL
  f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function 
configuration
  f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range
  77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration
  6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range
  90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID
  16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support 
for OCXL
  2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter 
contexts
  d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file 
descriptors for OCXL
  1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context 
discovery
  e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload 
policy modification
  5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU
  99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an 
adapter context
  d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific 
mappings
  8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling
  9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter 
VPD data
  b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link
  099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction 
layer
  5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element 
lifecycle
  0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt 
management
  ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt 
mapping and registration
  cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user 
contexts
  270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context 
polling
  302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context 
reading
  cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context 
mmap and release
  a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor 
mapping
  eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop
  c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user 
contexts
  bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master 
contexts
  e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous 
interrupt status bits
  dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context 
state machine
  9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation 
errors
  96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset
  966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations

  <<< The above is from my local git tree but it has been already sent
  to linux-scsi mailing list >>>

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

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

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

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

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

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

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

** Tags added: artful

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

Title:
  Night light does not work in some cases

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-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.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

--- Comment From fno...@us.ibm.com 2018-03-01 13:17 EDT---
(In reply to comment #28)
> (In reply to comment #27)
> > @paelzer yes, that is us agreeing with your plan
>
> Does it mean that we are not going to have HTM support on KVM guests, even
> in POWER8?

you would use the 2.10 machine type for that, right?

** Tags added: bugnameltc-165081 severity-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/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:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

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+

[Kernel-packages] [Bug 1751887] Re: The brightness of the screen cannot be adjusted with either the buttons or the slider.

2018-03-01 Thread albertoiNET

Bug exist on Kernel Upstream mainline

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

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

Title:
  The brightness of the screen cannot be adjusted with either the
  buttons or the slider.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness is always at 100% and cannot be adjusted with either the FN
  brightness buttons or the Unity top bar slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  albertoinet   1199 F pulseaudio
   /dev/snd/controlC0:  albertoinet   1199 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 20:49:16 2018
  HibernationDevice: RESUME=UUID=56535002-bba2-4658-b57f-75ba5bb87d4f
  InstallationDate: Installed on 2018-02-25 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Micro-Star International Co., Ltd. GT72VR 7RD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1785IMS.30E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1785
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1785IMS.30E:bd10/27/2017:svnMicro-StarInternationalCo.,Ltd.:pnGT72VR7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1785:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.family: GT
  dmi.product.name: GT72VR 7RD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1752672] Re: CAPI Flash (cxlflash) update

2018-03-01 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

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

** Tags added: triage-g

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

Title:
  CAPI Flash (cxlflash) update

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

Bug description:
  This is a feature for capi flash (cxlflash) inside the kernel.

  We have upstreamed the below 38 patches but they are not in the
  maintainers tree yet. I anticipate them to be available by Friday this
  week. I dont want to miss the boat for 18.04 feature code cutoff. Can
  you please suggest if I should submit these patches as SAUCE patches
  or can it be pulled from mainstream once maintainer pulls it in ?

  8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts
  8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context 
control register value
  44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier 
names
  9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend
  0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL
  f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function 
configuration
  f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range
  77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration
  6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range
  90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID
  16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support 
for OCXL
  2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter 
contexts
  d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file 
descriptors for OCXL
  1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context 
discovery
  e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload 
policy modification
  5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU
  99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an 
adapter context
  d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific 
mappings
  8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling
  9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter 
VPD data
  b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link
  099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction 
layer
  5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element 
lifecycle
  0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt 
management
  ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt 
mapping and registration
  cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user 
contexts
  270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context 
polling
  302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context 
reading
  cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context 
mmap and release
  a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor 
mapping
  eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop
  c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user 
contexts
  bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master 
contexts
  e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous 
interrupt status bits
  dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context 
state machine
  9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation 
errors
  96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset
  966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations

  <<< The above is from my local git tree but it has been already sent
  to linux-scsi mailing list >>>

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

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

[Kernel-packages] [Bug 1752680] [NEW] Night light does not work in some cases

2018-03-01 Thread Hrishikesh Barua

Public bug reported:

The night light feature does not work in these cases
 * Computer's screen shuts off due to timeout, and then is reactivated.
 * Computer is brought back from suspend
 * Computer desktop is locked, and unlocked using the password

In all these cases, the night light icon is present in the notification
area, and it says "Night Light On". But the screen temperature is that
of normal daylight.

In all these cases, disabling and re-enabling the night light using the
notification area icon reactivates the night light.

Version information

Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux

17.10 Artful Aardvark

Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
 /dev/snd/controlC0: talonx 2732 F pulseaudio
CurrentDesktop: GNOME-Classic:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
InstallationDate: Installed on 2016-05-05 (659 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Micro-Star International Co., Ltd. GP62 6QE
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-36.40-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.169.3
Tags: artful
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/25/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16J5IMS.113
dmi.board.asset.tag: Default string
dmi.board.name: MS-16J5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.A
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
dmi.product.name: GP62 6QE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

Title:
  Night light does not work in some cases

Status in linux package in Ubuntu:
  New

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A

[Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

D05 & QDF2400 errors are all expected, thanks Manoj!

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1752669] [NEW] iwlwifi 0000:01:00.0: fail to flush all tx fifo queues Q 0

2018-03-01 Thread Cristian Aravena Romero

Public bug reported:

Hello,

dmesg:
[17322.141897] iwlwifi :01:00.0: fail to flush all tx fifo queues Q 0
[17322.141980] iwlwifi :01:00.0: Queue 0 is active on fifo 3 and stuck for 
0 ms. SW [136, 137] HW [136, 137] FH TRB=0x080300088

Regards,
--
Cristian

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

** Affects: linux
 Importance: Unknown
 Status: Unknown

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


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

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

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

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

Title:
  iwlwifi :01:00.0: fail to flush all tx fifo queues Q 0

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

Bug description:
  Hello,

  dmesg:
  [17322.141897] iwlwifi :01:00.0: fail to flush all tx fifo queues Q 0
  [17322.141980] iwlwifi :01:00.0: Queue 0 is active on fifo 3 and stuck 
for 0 ms. SW [136, 137] HW [136, 137] FH TRB=0x080300088

  Regards,
  --
  Cristian

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

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

--- Comment From bren...@br.ibm.com 2018-03-01 12:41 EDT---
(In reply to comment #27)
> @paelzer yes, that is us agreeing with your plan

Does it mean that we are not going to have HTM support on KVM guests,
even in POWER8?

** Tags removed: bugnameltc-165081 kernel-da-key severity-critical
triage-g

-- 
You 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:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

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

[Kernel-packages] [Bug 1752672] [NEW] CAPI Flash (cxlflash) update

Public bug reported:

This is a feature for capi flash (cxlflash) inside the kernel.

We have upstreamed the below 38 patches but they are not in the
maintainers tree yet. I anticipate them to be available by Friday this
week. I dont want to miss the boat for 18.04 feature code cutoff. Can
you please suggest if I should submit these patches as SAUCE patches or
can it be pulled from mainstream once maintainer pulls it in ?

8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts
8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context 
control register value
44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier names
9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend
0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL
f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function 
configuration
f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range
77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration
6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range
90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID
16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support for 
OCXL
2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter 
contexts
d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file 
descriptors for OCXL
1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context 
discovery
e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload policy 
modification
5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU
99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an adapter 
context
d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific 
mappings
8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling
9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter VPD 
data
b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link
099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction layer
5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element 
lifecycle
0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt 
management
ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt 
mapping and registration
cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user 
contexts
270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context 
polling
302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context 
reading
cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context mmap 
and release
a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor 
mapping
eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop
c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user contexts
bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master 
contexts
e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous interrupt 
status bits
dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context state 
machine
9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation 
errors
96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset
966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations

<<< The above is from my local git tree but it has been already sent to
linux-scsi mailing list >>>

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


** Tags: architecture-ppc64le bugnameltc-163818 severity-medium 
targetmilestone-inin1804

** Tags added: architecture-ppc64le bugnameltc-163818 severity-medium
targetmilestone-inin1804

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

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

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

Title:
  CAPI Flash (cxlflash) update

Status in linux package in Ubuntu:
  New

Bug description:
  This is a feature for capi flash (cxlflash) inside the kernel.

  We have upstreamed the below 38 patches but they are not in the
  maintainers tree yet. I anticipate them to be available by Friday this
  week. I dont want to miss the boat for 18.04 feature code cutoff. Can
  you please suggest if I should submit these patches as SAUCE patches
  or can it be pulled from mainstream once maintainer pulls it in ?

  8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts

[Kernel-packages] [Bug 1752672] [NEW] CAPI Flash (cxlflash) update

2018-03-01 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

This is a feature for capi flash (cxlflash) inside the kernel.

We have upstreamed the below 38 patches but they are not in the
maintainers tree yet. I anticipate them to be available by Friday this
week. I dont want to miss the boat for 18.04 feature code cutoff. Can
you please suggest if I should submit these patches as SAUCE patches or
can it be pulled from mainstream once maintainer pulls it in ?

8d34234b7e44caa489bb7e684ead1f13b74faf72 cxlflash: Preserve number of 
interrupts for master contexts
8f20948fde0a06a283b39c3646c8060b62319875 cxlflash: Avoid clobbering context 
control register value
44569c367471bd57916798a701ad1c7250ec93fb cxlflash: Add argument identifier names
9e63cdb74178a02fa76c3896c2e38479148e60bf cxlflash: Introduce OCXL backend
0aa60ffb7ca4ce3f5cb33231d9358ab9f0ae9ec4 cxlflash: Hardware AFU for OCXL
f9e6817464036867a6994732c3b8b873b6fdc530 cxlflash: Read host function 
configuration
f1718592638ef1e3486ded07ba9aebf784b03db3 cxlflash: Setup function acTag range
77ece8688ed48e693bbdfef7b856ed146dac5838 cxlflash: Read host AFU configuration
6491b3338076c8a71f70c326aeacf7ecde139124 cxlflash: Setup AFU acTag range
90fbea09364d3a32b6b2b0fbbd56c4fbaabe5400 cxlflash: Setup AFU PASID
16e8be014d2efa0f7e713d5e7cfae9348eaab6fd cxlflash: Adapter context support for 
OCXL
2d431a892b91f9f004a8b6413d990c55dac6ac16 cxlflash: Use IDR to manage adapter 
contexts
d0dd47f71da4a9f37cfd2eced36f85c2751fcdf5 cxlflash: Support adapter file 
descriptors for OCXL
1719110f42503bcac6962daf4492cec3c16c325f cxlflash: Support adapter context 
discovery
e9ff19884da98139427e23c8ce3bed7614427fed cxlflash: Support image reload policy 
modification
5706f2a40306b2fe5ffae6fa1eacc81afed3fa11 cxlflash: MMIO map the AFU
99b7d36979c67708851f8058c9fb6e412d32577b cxlflash: Support starting an adapter 
context
d8e72cf527fed71641dd011dff13fbd1e5fad2da cxlflash: Support process specific 
mappings
8cc796025b082c13c1ec3db620e9f23f6082726a cxlflash: Support AFU state toggling
9e0d9716935bdf9e2c24d3c27ae8be1756eff46e cxlflash: Support reading adapter VPD 
data
b37e0fdd868e47221e706be4d51c66e5e9224f20 cxlflash: Setup function OCXL link
099858c80b956752693e0d3bb8f01618a11d48dc cxlflash: Setup OCXL transaction layer
5b1a1f3d49ee4b41778e41bf8147febc885df381 cxlflash: Support process element 
lifecycle
0e3e9fbfada4506620610497cdc6ce0a0b3cdff2 cxlflash: Support AFU interrupt 
management
ff7388a91f3739c5420b16f20d74644f5da9b03a cxlflash: Support AFU interrupt 
mapping and registration
cfa71c77fd9e440b1d8f105151eaf30aff5f3241 cxlflash: Support starting user 
contexts
270a401d0901eeb736b1da4fd728006ae4d40145 cxlflash: Support adapter context 
polling
302ce17cba275e295803a2a2aad83debfd02cf5d cxlflash: Support adapter context 
reading
cc8640bac30541ddc453834d5956ced223ed0020 cxlflash: Support adapter context mmap 
and release
a071c05a8cab915a3a7d11a87b06da00bc5bc7d5 cxlflash: Support file descriptor 
mapping
eb01b23138c73967c17c04e79ab4c5df4649984e cxlflash: Introduce object handle fop
c6a2e3b15bd5a6f85472eac54fede0cffcd6d4e5 cxlflash: Setup LISNs for user contexts
bbfdb7e4d852d213b3b474185918a94aabecad7f cxlflash: Setup LISNs for master 
contexts
e8d361505cef408ec3afb5f0cf1e4c3fd7f6150b cxlflash: Update synchronous interrupt 
status bits
dc8e5211cbd6457f618bc49df7e769895b6996bc cxlflash: Introduce OCXL context state 
machine
9c5567f5e9c92a9f94f7790b2dd905235bc9842c cxlflash: Register for translation 
errors
96cacd8347f27d258bae75d796cc1f523724a37a cxlflash: Support AFU reset
966a6e64ddd9624999d895fffab190c7d2f96c85 cxlflash: Enable OCXL operations

<<< The above is from my local git tree but it has been already sent to
linux-scsi mailing list >>>

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


** Tags: architecture-ppc64le bugnameltc-163818 severity-medium 
targetmilestone-inin1804
-- 
CAPI Flash (cxlflash) update
https://bugs.launchpad.net/bugs/1752672
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 1750385] Re: Poor wifi signal with RTL8723BE and 4.13.0-32 kernel

2018-03-01 Thread Doesnt Matter

I have the bluetooth adapter powered off in Manjaro but I also have it
powered off in Mint (I did not check the bluetooth state in the live
ubuntu-image on the USB though).

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

Title:
  Poor wifi signal with RTL8723BE and 4.13.0-32 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using Linux Mint 18.3 alongside with the 4.13.0-32 kernel the
  wifi signal is really really poor (while almost sitting on the
  respective router) whereas with the 4.10.0-38 it works like charm.

  I had to use a configuration file for getting the wifi to work
  properly (/etc/modprobe.d/rtl8723be.conf: options rtl8723be fwlps=0
  ips=0 ant_sel=1) but chaning the antenna from 1 to 0 did not change
  anything with the 4.13 kernel.

  I am also running Manjaro Linux with the 4.14 kernel on my machine
  where the wifi is also working just fine (with antenna 0 though).

  cat /proc/version_signature:
  Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17

  (I tried using ubuntu-bug linux but it didn't work [The report belongs
  to a package that is not installed.])

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

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

[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools

2018-03-01 Thread Colin Ian King

** Changed in: thunderbolt-tools (Ubuntu)
   Importance: High => Critical

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

Title:
   [MIR] thunderbolt-tools

Status in thunderbolt-tools package in Ubuntu:
  Confirmed

Bug description:
  == Overview ==

  Intel Thunderbolt userspace components provides components for using
  Intel Thunderbolt controllers with security level features.
  Thunderbolt™ technology is a transformational high-speed, dual
  protocol I/O that provides unmatched performance with up to 40Gbps bi-
  directional transfer speeds. It provides flexibility and simplicity by
  supporting both data (PCIe, USB3.1) and video (DisplayPort) on a
  single cable connection that can daisy-chain up to six devices.

  [ See https://github.com/intel/thunderbolt-software-user-space ]

  == Answers to UbuntuMainInclusionRequirements ==

  = Requirements =

  1. Availability
 Package is in universe: 
https://launchpad.net/ubuntu/+source/thunderbolt-tools

  2. Rationale
 Package a device enabler for users with Thunderbolt technology

  3. Security:
 No security issues exposed so far. However, the tools have only been in 
Ubuntu since
 2017-12-09, so this currently is less than the 90 days threshold.

  4. Quality assurance:
 * Manual is provided
 * No debconf questions higher than medium
 * No major outstanding bugs. I'm also helping Intel fix issues that I'm 
finding with
   static analysis tools such as scan-build, cppcheck and CoverityScan
   Bugs outstanding:
 #883857 please backport for stretch-backports
 #882525 thunderbolt-tools: FTBFS on kFreeBSD: 
_ZN5boost6system15system_categoryEv undefined
   - I can fix this, but it makes no sense to run on kFreeBSD
 * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an 
industry standard
   and the support for the tools are in the 4.13+ kernels
 * No Test Suite shipped with the package
 * Does not rely on obsolete or demoted packages

  5. UI standards:
 * This is a CLI tool. Tool has normal CLI style short help and man pages
 * No desktop file required as it is a CLI tool.

  6. Binary Dependencies:
libboost-dev(main)
libboost-filesystem-dev (main)
libboost-program-options-dev(main)
udev(main)

  7. Standards compliance:
 lintian clean and meets the FHS + Debian Policy standards to the best of 
my knowledge

  8. Maintenance
 * Package owning team: The Ubuntu Kernel Team
 * Debian package maintained by Colin Ian King (myself from the Kernel Team)

  9. Background Information
 The user-space components implement device approval support:

 a. Easier interaction with the kernel module for approving connected 
devices.
 b. ACL for auto-approving devices white-listed by the user.

 Tools provided by this package:

  tbtacl - triggered by udev (see the udev rules in tbtacl.rules).
  It auto-approves devices that are found in ACL.

  tbtadm - user-facing CLI tool. It provides operations for device
  approval, handling the ACL and more.

  The user-space components operate in coordination with the
  upstream Thunderbolt kernel driver (found in v4.13) to provide the
  Thunderbolt functionalities. These components are NOT compatible with
  the old out-of-tree Thunderbolt kernel module.

  = Security checks =

http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability 
Database using the package as a keyword
* No CVEs found

http://secunia.com/advisories/search/: search for the package as a keyword
* No security advisories found

Ubuntu CVE Tracker
  http://people.ubuntu.com/~ubuntu-security/cve/main.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/universe.html
  * No
  http://people.ubuntu.com/~ubuntu-security/cve/partner.html
  * No

  Check for security relevant binaries. If any are present, this
  requires a more in-depth security review.

  Executables which have the suid or sgid bit set.
* Not applicable

  Executables in /sbin, /usr/sbin.
* None in these paths

  Packages which install daemons (/etc/init.d/*)
* No

  Packages which open privileged ports (ports < 1024).
* No

   Add-ons and plugins to security-sensitive software (filters,
   scanners, UI skins, etc)
* This does exec tbtacl from udev with new udev rules, so this
  needs security checking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions

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

[Kernel-packages] [Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly

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

** Changed in: linux (Ubuntu Artful)
   Status: New => 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/1482390

Title:
  ASUS UX305LA - Battery state not detected correctly

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===

  Whether the AC adapter is connected or not, the battery is always
  detected as discharging:

  When AC adapter is present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%
    AC adapter : online

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54027 mWh, 100.0%
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 0 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  When AC adapter is not present:

  $ sudo acpitool -a -b
    Battery #1 : Discharging, 100.0%, 04:19:49
    AC adapter : off-line

  $ sudo acpitool -B
    Battery #1 : present
  Remaining capacity : 54005 mWh, 100.0%, 04:28:31
  Design capacity: 56041 mWh
  Last full capacity : 53507 mWh, 95.48% of design capacity
  Capacity loss  : 4.522%
  Present rate   : 12067 mW
  Charging state : Discharging
  Battery type   : Li-ion
  Model number   : ASUS

  System information:

  $ sudo dmidecode
  # dmidecode 2.12
  # SMBIOS entry point at 0xace2a898
  SMBIOS 2.8 present.
  27 structures occupying 2154 bytes.
  Table at 0xAC7C6000.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
   Vendor: American Megatrends Inc.
   Version: UX305LA.202
   Release Date: 04/16/2015
   Address: 0xF
   Runtime Size: 64 kB
   ROM Size: 6464 kB
   Characteristics:
    PCI is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    Smart battery is supported
    BIOS boot specification is supported
    Targeted content distribution is supported
    UEFI is supported
   BIOS Revision: 5.6

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   UUID: xxx
   Wake-up Type: Power Switch
   SKU Number: ASUS-NotebookSKU
   Family: UX

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: UX305LA
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis: MIDDLE
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 25 bytes
  Chassis Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Type: Notebook
   Lock: Not Present
   Version: 1.0
   Serial Number: xxx
   Asset Tag: xxx
   Boot-up State: Safe
   Power Supply State: Safe
   Thermal State: Safe
   Security Status: None
   OEM Information: 0x
   Height: Unspecified
   Number Of Power Cords: 1
   Contained Elements: 1
     (0)
   SKU Number: To be filled by O.E.M.

  Handle 0x0004, DMI type 10, 26 bytes
  On Board Device 1 Information
   Type: Video
   Status: Enabled
   Description:  VGA
  On Board Device 2 Information
   Type: Ethernet
   Status: Enabled
   Description:  GLAN
  On Board Device 3 Information
   Type: Ethernet
   Status: Enabled
   Description:  WLAN
  On Board Device 4 Information
   Type: Sound
   Status: Enabled
   Description:  Audio CODEC
  On Board Device 5 Information
   Type: SATA Controller
   Status: Enabled
   Description:  SATA Controller
  On Board Device 6 Information
   Type: Other
   Status: Enabled
   Description:  USB 2.0 Controller
  On Board Device 7 Information
   Type: Other
   Status: Enabled
   Description:

[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged

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

** Changed in: linux (Ubuntu Artful)
   Status: New => 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/1661876

Title:
  [Asus UX360UA] battery status in unity-panel is not changing when
  battery is being charged

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, 
alongside with Windows 10. I've already installed the updates meanwhile.

  When I start charging my computer the battery icon on the unity-panel
  is not changing (it stays in the 98% complete).

  This is strange because this is a fresh installation so I didn't change any 
configuration yet. Also, when I tried this ubuntu in the live pen, I noticed 
that the icon changed when I started charging the laptop. That's why I think it 
is a bug.
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tjiagom1806 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
  InstallationDate: Installed on 2017-02-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-62-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/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX360UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

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

** Changed in: linux (Ubuntu Artful)
   Status: New => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1747896] Re: OOM and High CPU utilization in update_blocked_averages because of too many cfs_rqs in rq->leaf_cfs_rq_list

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

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

Title:
  OOM and High CPU utilization in update_blocked_averages because of too
  many cfs_rqs in rq->leaf_cfs_rq_list

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

Bug description:
  [Impact]
  The CPU utilization keeps high and the flamegraph[1] shows that the CPU
  is busy updating the load average in the for loop inside
  update_blocked_averages() function. Also, the OOM happens because of
  the decayed cfs_rqs are not released.

  [Fix]
  commit a9e7f6544b9cebdae54d29f87a7ba2a83c0471b5
  Author: Tejun Heo 
  Date:   Tue Apr 25 17:43:50 2017 -0700

  sched/fair: Fix O(nr_cgroups) in load balance path
  
  Currently, rq->leaf_cfs_rq_list is a traversal ordered list of all
  live cfs_rqs which have ever been active on the CPU; unfortunately,
  this makes update_blocked_averages() O(# total cgroups) which isn't
  scalable at all.
  
  This shows up as a small CPU consumption and scheduling latency
  increase in the load balancing path in systems with CPU controller
  enabled across most cgroups.  In an edge case where temporary cgroups
  were leaking, this caused the kernel to consume good several tens of
  percents of CPU cycles running update_blocked_averages(), each run
  taking multiple millisecs.
  
  This patch fixes the issue by taking empty and fully decayed cfs_rqs
  off the rq->leaf_cfs_rq_list. 

  [Test]
  1). Running the script
  #/bin/bash

  for i in $(seq 1 10); do
  ( for j in $(seq 1 3000); do ssh -S none u@localhost date;done; echo 
"done $i" ) &
  done

  2). Observe the cfs_rqs
  $ watch -n1 "grep cfs_rq /proc/sched_debug| wc -l"

  3). Observe the CPU utilization rate
  $ sudo htop

  The patched kernel[2] shows that the CPU utilization rate is normal, the
  cfs_rqs is decreased periodically, and the memory can be limited.

  [Reference]
  [1]. 
http://kernel.ubuntu.com/~gavinguo/168887/2018-01-31_07-38-45.perf.data.svg
  [2]. https://launchpad.net/~mimi0213kimo/+archive/ubuntu/cfs-rq-clean

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

-- 
Mailing list: https://launchpad.net/~kernel-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] [NEW] retpoline: ignore %cs:0xNNN constant indirections

2018-03-01 Thread Andy Whitcroft

Public bug reported:

These are paravirt style indirections and can be ignored.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

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

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

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Artful:
  New

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 1751098] Re: Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1751098

Title:
  Ubuntu hangs shortly after booting with kernel 4.13.0-36

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

Bug description:
  After upgrading to linux 4.13.0-36 my laptop hangs shortly after
  booting, even before logging in to the desktop. It starts with the
  interface being unresponsive but the mouse cursor moving, and shortly
  after that the mouse cursor also hangs intermittently and then
  permanently.

  Linux 4.13.0-32 works fine.

  My laptop is a Dell XPS 13 9360 with an Core i5 7200u.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USUARIOORDEN DE ACCESO PID
   /dev/snd/controlC0:  nicolas2111 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 10:56:06 2018
  InstallationDate: Installed on 2018-02-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=452f690d-29d8-46b1-88a4-4262b6d20734 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.2
  dmi.board.name: 05HM5Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y: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/1751098/+subscriptions

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

Re: [Kernel-packages] [Bug 1749040] Re: KPTI support for arm64 systems

On Thu, Mar 1, 2018 at 8:50 AM, Paolo Pisati <1749...@bugs.launchpad.net> wrote:
> I see 5 failures marked as blocker there: 4 couldn't complete due to the
> test environment, and 1[*], apparently, is a CONFIG issue (so something
> that predates this patchset).

Sorry - I didn't have time to analyze it last night when I posted. All
5 are expected:
  - disk/disk_stress_ng_sda is a test bug (LP: #1751167)
  - ethernet/multi_iperf3_* requires a client/server setup we don't
have in place
  - miscellanea/bmc_info - this system doesn't have a conventional BMC
  - miscellanea/efi_boot_mode - this system boots w/ u-boot
  - miscellanea/ipmi_test - this system doesn't have a conventional BMC

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

Title:
  KPTI support for arm64 systems

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

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush