[Kernel-packages] [Bug 159356] Re: When DMA is disabled system freeze on high memory usage

2019-03-23 Thread Dima
Just a little note. Probably it is not DMA related issue as it entitled.
I found it happening with zram swap too.

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

Title:
  When DMA is disabled system freeze on high memory usage

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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


[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2019-03-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [] do_one_initcall+0x50/0x1a0
  [   11.397431]  [] ? parse_args+0x2cf/0x490
  [   11.399313]  [] kernel_init_freeable+0x178/0x217
  [   11.402112]  [] kernel_init+0xe/0x100
  [   11.404013]  [] ret_from_fork+0x1f/0x40
  [   11.405895]  [] ? rest_init+0x80/0x80
  [   11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 
48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

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

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


[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)

2019-03-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  CPU fan goes full throttle triggered by waking up from suspend on
  Lenovo X1 Carbon (4th Gen., 2016)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Zesty:
  Expired

Bug description:
  This is a copy of a very similar bug report which is currently marked
  as triaged and where my comment is ignored maybe because of that.

  Please see my additional remarks at the end of this report.

  ---
  Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running 
Ubuntu 17.04 has its fan go full steam if the laptop is woken up from 
sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or 
silent, even for hours.

  The bug has been fixed upstream, see

  6625914 ACPI / EC: Drop EC noirq hooks to fix a regression
  9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression

  and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129
  (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181)

  and I hope this fix will make its way into a near-future kernel update
  to ubuntu :)

  Many thanks!
  ---

  Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616

  Additional remarks:

  - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the 
bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 
5th Gen.
  - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who 
run the HWE kernel on Ubuntu 16.04 LTS will have this problem too!

  I can reproduce it on my local system which has "linux-image-generic-
  hwe-16.04" installed (4.10.0.32.34).

  Reading through the comments, it's not exactly clear to me which of
  the commits has fixed this problem, but I guess that the following two
  changes have made the difference:

  https://patchwork.kernel.org/patch/9835823/
  https://patchwork.kernel.org/patch/9835825/

  I am reporting this as a new issue because the fixes from 4.13 need to
  be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel.

  Many thanks!

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

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


[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)

2019-03-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu Zesty) because there has been no activity for
60 days.]

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

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

Title:
  CPU fan goes full throttle triggered by waking up from suspend on
  Lenovo X1 Carbon (4th Gen., 2016)

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Zesty:
  Expired

Bug description:
  This is a copy of a very similar bug report which is currently marked
  as triaged and where my comment is ignored maybe because of that.

  Please see my additional remarks at the end of this report.

  ---
  Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running 
Ubuntu 17.04 has its fan go full steam if the laptop is woken up from 
sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or 
silent, even for hours.

  The bug has been fixed upstream, see

  6625914 ACPI / EC: Drop EC noirq hooks to fix a regression
  9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression

  and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129
  (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181)

  and I hope this fix will make its way into a near-future kernel update
  to ubuntu :)

  Many thanks!
  ---

  Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616

  Additional remarks:

  - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the 
bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 
5th Gen.
  - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who 
run the HWE kernel on Ubuntu 16.04 LTS will have this problem too!

  I can reproduce it on my local system which has "linux-image-generic-
  hwe-16.04" installed (4.10.0.32.34).

  Reading through the comments, it's not exactly clear to me which of
  the commits has fixed this problem, but I guess that the following two
  changes have made the difference:

  https://patchwork.kernel.org/patch/9835823/
  https://patchwork.kernel.org/patch/9835825/

  I am reporting this as a new issue because the fixes from 4.13 need to
  be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel.

  Many thanks!

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

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


[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

2019-03-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  Expired

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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


[Kernel-packages] [Bug 1796355] Re: USB-C ValueLine network adapter fails to connect

2019-03-23 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  USB-C ValueLine network adapter fails to connect

Status in linux package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  The adapter I'm trying to use using is a 'Valueline' USB-C adapter,
  with no external identifying information. lsusb lists it as

  Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp.

  It works fine on a Windows 10 system (same hardware platform), where
  it's identified as a 10/100/1000 Realtek adapter.

  When I connect it to my system (Asus Zenbook UX490UA) internal lights
  go on, but no connection is produced.  The network icon (upper right)
  is shown briefly, then disappears, the is show, then disappears.
  After some time it seems to give up.

  Kernel logs show repeated occurrences of:

  Oct  5 17:02:22 athasus kernel: [  317.843590] usb 4-2: new SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  317.863719] usb 4-2: New USB device found, 
idVendor=0bda, idProduct=8153
  Oct  5 17:02:22 athasus kernel: [  317.863728] usb 4-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=6
  Oct  5 17:02:22 athasus kernel: [  317.863735] usb 4-2: Product: USB 
10/100/1000 LAN
  Oct  5 17:02:22 athasus kernel: [  317.863741] usb 4-2: Manufacturer: Realtek
  Oct  5 17:02:22 athasus kernel: [  317.863745] usb 4-2: SerialNumber: 
0100
  Oct  5 17:02:22 athasus kernel: [  318.000268] usb 4-2: reset SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  318.057875] r8152 4-2:1.0 eth0: v1.09.9
  Oct  5 17:02:22 athasus kernel: [  318.138042] r8152 4-2:1.0 enxa0cec809bf58: 
renamed from eth0
  Oct  5 17:02:22 athasus kernel: [  318.170397] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.176359] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.354745] r8152 4-2:1.0 enxa0cec809bf58: 
Stop submitting intr, status -71
  Oct  5 17:02:22 athasus kernel: [  318.543737] usb 4-2: USB disconnect, 
device number 121

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 17:35:17 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-03 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   TIMESTAMP-REAL 
   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
   SLAVE 
   ATH   79577e92-4b01-46c4-bbff-2088aaf0750a  wifi  1538753528  fre  5 okt 
2018 17:32:08  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  ATH  
   79577e92-4b01-46c4-bbff-2088aaf0750a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Kernel-packages] [Bug 1796355] Re: USB-C ValueLine network adapter fails to connect

2019-03-23 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  USB-C ValueLine network adapter fails to connect

Status in linux package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  The adapter I'm trying to use using is a 'Valueline' USB-C adapter,
  with no external identifying information. lsusb lists it as

  Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp.

  It works fine on a Windows 10 system (same hardware platform), where
  it's identified as a 10/100/1000 Realtek adapter.

  When I connect it to my system (Asus Zenbook UX490UA) internal lights
  go on, but no connection is produced.  The network icon (upper right)
  is shown briefly, then disappears, the is show, then disappears.
  After some time it seems to give up.

  Kernel logs show repeated occurrences of:

  Oct  5 17:02:22 athasus kernel: [  317.843590] usb 4-2: new SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  317.863719] usb 4-2: New USB device found, 
idVendor=0bda, idProduct=8153
  Oct  5 17:02:22 athasus kernel: [  317.863728] usb 4-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=6
  Oct  5 17:02:22 athasus kernel: [  317.863735] usb 4-2: Product: USB 
10/100/1000 LAN
  Oct  5 17:02:22 athasus kernel: [  317.863741] usb 4-2: Manufacturer: Realtek
  Oct  5 17:02:22 athasus kernel: [  317.863745] usb 4-2: SerialNumber: 
0100
  Oct  5 17:02:22 athasus kernel: [  318.000268] usb 4-2: reset SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  318.057875] r8152 4-2:1.0 eth0: v1.09.9
  Oct  5 17:02:22 athasus kernel: [  318.138042] r8152 4-2:1.0 enxa0cec809bf58: 
renamed from eth0
  Oct  5 17:02:22 athasus kernel: [  318.170397] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.176359] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.354745] r8152 4-2:1.0 enxa0cec809bf58: 
Stop submitting intr, status -71
  Oct  5 17:02:22 athasus kernel: [  318.543737] usb 4-2: USB disconnect, 
device number 121

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 17:35:17 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-03 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   TIMESTAMP-REAL 
   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
   SLAVE 
   ATH   79577e92-4b01-46c4-bbff-2088aaf0750a  wifi  1538753528  fre  5 okt 
2018 17:32:08  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  ATH  
   79577e92-4b01-46c4-bbff-2088aaf0750a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Kernel-packages] [Bug 1821053] Re: [disco] [5.0.0-7.8] can't mount guest cifs share

2019-03-23 Thread Andreas Hasenack
I installed linux-source in disco, applied those two patches to the
source tree, copied the config file from /boot and rebuilt the kernel,
rebooted, and can confirm the bug is fixed.

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

Title:
  [disco] [5.0.0-7.8] can't mount guest cifs share

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  with a simple smb.conf setup like this:
  [pub]
  path = /pub
  guest ok = yes

  The following mount command fails when the running kernel is 5.0.0-7:
  root@ubuntu:~# dmesg -C
  root@ubuntu:~# mount //localhost/pub /mnt -o guest
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  root@ubuntu:~# dmesg
  [  178.469307] CIFS: Attempting to mount //localhost/pub
  [  178.469343] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.
  [  178.481741] CIFS VFS: failed to connect to IPC (rc=-13)
  [  178.485272] CIFS VFS: cifs_mount failed w/return code = -13

  samba server logs, in debug 5, show:
  [2019/03/20 17:25:19.365445,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.365524,  0] ../../lib/util/util.c:508(dump_data)
[] A6 62 5F 50 9C D7 31 42   14 34 52 9F AA 49 C8 31   .b_P..1B .4R..I.1
  [2019/03/20 17:25:19.365562,  0] ../../lib/util/util.c:508(dump_data)
[] 31 37 12 A2 D5 D4 59 99   0B 63 C5 21 EB 86 70 74   17Y. .c.!..pt
  [2019/03/20 17:25:19.369055,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.369092,  0] ../../lib/util/util.c:508(dump_data)
[] 23 2C 4F 10 0E 4E 46 2E   8A 5B E3 70 0F B3 D3 FB   #,O..NF. .[.p
  [2019/03/20 17:25:19.369120,  0] ../../lib/util/util.c:508(dump_data)
[] 50 F7 C6 8A 6E BC B2 B7   1C 2F 43 30 90 6A 25 CA   P...n... ./C0.j%.

  
  With kernel 4.19.0-12-generic, the exact same system, the command works:

  root@ubuntu:~# dmesg -C

  root@ubuntu:~# mount //localhost/pub /mnt -o guest

  root@ubuntu:~# dmesg
  [  277.745885] FS-Cache: Loaded
  [  277.768408] FS-Cache: Netfs 'cifs' registered for caching
  [  277.768495] Key type cifs.spnego registered
  [  277.768498] Key type cifs.idmap registered
  [  277.768707] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.

  root@ubuntu:~# mount -t cifs
  //localhost/pub on /mnt type cifs 
(rw,relatime,vers=default,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  root@ubuntu:~# uname -r
  4.19.0-12-generic

  
  Just looking at the list of patches queued up for the next upstream kernel 
release, at 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0,
 this one looks promising:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch


  I can easily test a new kernel for you.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 18:04 seq
   crw-rw 1 root audio 116, 33 Mar 20 18:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  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
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=PARTUUID=e2b8e290-77c5-437c-a78d-b59424881b58 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic 

[Kernel-packages] [Bug 1821053] Re: [disco] [5.0.0-7.8] can't mount guest cifs share

2019-03-23 Thread Andreas Hasenack
These two patches applied in that order fix the issue:

https://lore.kernel.org/linux-cifs/20190321045902.14326-1-lsahl...@redhat.com/t/#u
https://lore.kernel.org/linux-cifs/cah2r5ms_md9uosm5x0acamtz2zhiu0+hvvzzjf2pgzqyxny...@mail.gmail.com/

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

Title:
  [disco] [5.0.0-7.8] can't mount guest cifs share

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  with a simple smb.conf setup like this:
  [pub]
  path = /pub
  guest ok = yes

  The following mount command fails when the running kernel is 5.0.0-7:
  root@ubuntu:~# dmesg -C
  root@ubuntu:~# mount //localhost/pub /mnt -o guest
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  root@ubuntu:~# dmesg
  [  178.469307] CIFS: Attempting to mount //localhost/pub
  [  178.469343] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.
  [  178.481741] CIFS VFS: failed to connect to IPC (rc=-13)
  [  178.485272] CIFS VFS: cifs_mount failed w/return code = -13

  samba server logs, in debug 5, show:
  [2019/03/20 17:25:19.365445,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.365524,  0] ../../lib/util/util.c:508(dump_data)
[] A6 62 5F 50 9C D7 31 42   14 34 52 9F AA 49 C8 31   .b_P..1B .4R..I.1
  [2019/03/20 17:25:19.365562,  0] ../../lib/util/util.c:508(dump_data)
[] 31 37 12 A2 D5 D4 59 99   0B 63 C5 21 EB 86 70 74   17Y. .c.!..pt
  [2019/03/20 17:25:19.369055,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.369092,  0] ../../lib/util/util.c:508(dump_data)
[] 23 2C 4F 10 0E 4E 46 2E   8A 5B E3 70 0F B3 D3 FB   #,O..NF. .[.p
  [2019/03/20 17:25:19.369120,  0] ../../lib/util/util.c:508(dump_data)
[] 50 F7 C6 8A 6E BC B2 B7   1C 2F 43 30 90 6A 25 CA   P...n... ./C0.j%.

  
  With kernel 4.19.0-12-generic, the exact same system, the command works:

  root@ubuntu:~# dmesg -C

  root@ubuntu:~# mount //localhost/pub /mnt -o guest

  root@ubuntu:~# dmesg
  [  277.745885] FS-Cache: Loaded
  [  277.768408] FS-Cache: Netfs 'cifs' registered for caching
  [  277.768495] Key type cifs.spnego registered
  [  277.768498] Key type cifs.idmap registered
  [  277.768707] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.

  root@ubuntu:~# mount -t cifs
  //localhost/pub on /mnt type cifs 
(rw,relatime,vers=default,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  root@ubuntu:~# uname -r
  4.19.0-12-generic

  
  Just looking at the list of patches queued up for the next upstream kernel 
release, at 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0,
 this one looks promising:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch


  I can easily test a new kernel for you.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 18:04 seq
   crw-rw 1 root audio 116, 33 Mar 20 18:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  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
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=PARTUUID=e2b8e290-77c5-437c-a78d-b59424881b58 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2019-03-23 Thread Bug Watch Updater
** Changed in: linux
   Status: Incomplete => Confirmed

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1727662]

2019-03-23 Thread Johan-freedesktop
Would appreciate feedback on the data given, if more is needed or if a
separate bug report should be filed. 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/1727662

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker

2019-03-23 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oracle - 4.15.0-1010.12

---
linux-oracle (4.15.0-1010.12) bionic; urgency=medium

  * linux-oracle: 4.15.0-1010.12 -proposed tracker (LP: #1819704)

  * hot add VF to net_failover - could not rename interface '8' from 'eth0' to
'ens4': Device or resource busy (LP: #1815268)
- SAUCE: net_failover: delay taking over primary device to accommodate udevd
  renaming

  [ Ubuntu: 4.15.0-47.50 ]

  * linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
  * C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
  * arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
  * Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
  * CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
  * CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
  * amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
  * tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
  * CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
  * raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
  adjustments are in progress
  * [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
  * CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
  paths
- bpf: add various test cases to selftests
  * CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
  * BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
  * squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
  * efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
  * Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
  * ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
  * Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
  * CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
  * CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
  * CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in 
card.c
  * CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
  * Bionic update: upstream stable patchset 2019-02-08 (LP: #1815234)
- fork: unconditionally clear stack on fork
- spi: spi-s3c64xx: Fix system resume support
- Input: elan_i2c - add ACPI ID for lenovo ideapad 330
- Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
- Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
- kvm, mm: account shadow page tables to kmemcg
- delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
- tracing: Fix double 

[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-03-23 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oracle - 4.15.0-1010.12

---
linux-oracle (4.15.0-1010.12) bionic; urgency=medium

  * linux-oracle: 4.15.0-1010.12 -proposed tracker (LP: #1819704)

  * hot add VF to net_failover - could not rename interface '8' from 'eth0' to
'ens4': Device or resource busy (LP: #1815268)
- SAUCE: net_failover: delay taking over primary device to accommodate udevd
  renaming

  [ Ubuntu: 4.15.0-47.50 ]

  * linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
  * C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
  * arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
  * Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
  * CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
  * CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
  * amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Don't use dc_link in link_encoder
- drm/amd/display: Move wait for hpd ready out from edp power control.
- drm/amd/display: eDP sequence BL off first then DP blank.
- drm/amd/display: Fix unused variable compilation error
- drm/amd/display: Fix warning about misaligned code
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
  * tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
  * CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
  * raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
(LP: #1811194)
- selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock
  adjustments are in progress
  * [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
  * CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
  paths
- bpf: add various test cases to selftests
  * CVE-2017-5753
- bpf: properly enforce index mask to prevent out-of-bounds speculation
- bpf: fix inner map masking to prevent oob under speculation
  * BPF: kernel pointer leak to unprivileged userspace (LP: #1815259)
- bpf/verifier: disallow pointer subtraction
  * squashfs hardening (LP: #1816756)
- squashfs: more metadata hardening
- squashfs metadata 2: electric boogaloo
- squashfs: more metadata hardening
- Squashfs: Compute expected length from inode size rather than block length
  * efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
  * Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
  * ipset kernel error: 4.15.0-43-generic (LP: #1811394)
- netfilter: ipset: Fix wraparound in hash:*net* types
  * Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
  * CVE-2018-18021
- arm64: KVM: Tighten guest core register access from userspace
- KVM: arm/arm64: Introduce vcpu_el1_is_32bit
- arm64: KVM: Sanitize PSTATE.M when being set from userspace
  * CVE-2018-14678
- x86/entry/64: Remove %ebx handling from error_entry/exit
  * CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in 
card.c
  * CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
  * Bionic update: upstream stable patchset 2019-02-08 (LP: #1815234)
- fork: unconditionally clear stack on fork
- spi: spi-s3c64xx: Fix system resume support
- Input: elan_i2c - add ACPI ID for lenovo ideapad 330
- Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
- Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
- kvm, mm: account shadow page tables to kmemcg
- delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
- tracing: Fix double 

[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)

2019-03-23 Thread Matheus
also just happened on the -42 version now... Seems like was less likely
to happen in older versions. I remember 2 months ago I made more than 10
hibernation cycles. Not sure whats happening now...

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

Title:
  s2disk freezes at saving image to disk (hibernation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1
  hibernation was working flawlessly on my machine. (with kernel
  4.15-46! not a kernel issue then?)

  Another thing that got updated recently was nvidia drivers which were
  known to cause hibernation issues, but those were on restoring the
  snapshot.

  http://imgur.com/gallery/jOyHEcL  --> I get stuck on this screen after
  running hibernate or pm-hibernate. (sys-req REISUB combination works
  there and is the only good way to restart I found)

  
  SPECS

  Laptop Dell Inspiron 7567 A30P
  Intel Core i7-7700HQ
  1x 16 GB DDR4 
  1 TB HDD + 256 GB SSD 
  Nvidia GeForce GTX 1050 
  Ti FHD display 
  Intel Dual Band Wireless AC 3165 
  1x1 Motherboard: 
  Intel HM175 Graphics adapter: 
  NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, 
  Core: 1620 MHz, 
  Memory: 1752 MHz, 
  GDDR5, 21.21.13.7320 (ForceWare 373.20), 
  Nvidia Optimus

  nvidia driver: 415.27

  INFO

  # uname -a
  Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed 
Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  # free -m
totalusedfree  shared  buff/cache   
available
  Mem:  1590629258742 1614238   
12485
  Swap: 16333   0   16333

  # cat /etc/fstab | grep swap
  # swap was on /dev/sda8 during installation
  UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw  
0   0
  n

  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernate 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hiber 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep s2disk
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernation

  
  I could find nothing scrolling up on syslog about the hibernation process or 
with grep 

  
  An interesting Note is that if I run hibernate just after I boot, it works 
and resumes perfectly! But after some system usage it randomly has that problem 
if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 
once.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   matheus   25949 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matheus   25949 F...m pulseaudio
   /dev/snd/controlC0:  matheus   25949 F pulseaudio
   /dev/snd/seq:matheus4986 f qsynth
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06
  InstallationDate: Installed on 2018-05-10 (308 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug 
no_console_suspend systemd.log_level=info nvidia-drm.modeset=0
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

2019-03-23 Thread Andy Smith
As mentioned in my first comment, this bug also affects the netboot
installer at e.g.
http://gb.archive.ubuntu.com/ubuntu/dists/bionic/main/installer-i386/current/images/
so it is still not possible to boot the installer in 32-bit under Xen.
The main OS kernel has been fixed but not the installer kernel. Who do
we need to speak to in order to get that kernel fixed?

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

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

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

Bug description:
  == SRU Justification ==
  After an upgrade to Bionic, the bug reporter states the 32-bit kernel
  does not boot under Xen PV mode.  This bug does not affect 64-bit
  kernels and if fixed by mainline commit 6a92b11169a6.

  == Fix ==
  6a92b11169a6 ("x86/EISA: Don't probe EISA bus for Xen PV guests")

  == Regression Potential ==
  Low.  This commit only affects x86 kernels.  This commit has also been cc'd 
to upstream stable, so it has had
  additional upstream review.

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

  
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it now 
refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 

  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

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


[Kernel-packages] [Bug 1820605] Re: linux-azure: 5.0.0-1001.1 -proposed tracker

2019-03-23 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
- phase: Promote to Proposed
- phase-changed: Wednesday, 20. March 2019 12:03 UTC
+ phase: Testing
+ phase-changed: Saturday, 23. March 2019 21:37 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Stalled -- packages no longer available
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   stakeholder-signoff: Pending -- waiting for signoff

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

Title:
  linux-azure: 5.0.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Disco:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
  phase: Testing
  phase-changed: Saturday, 23. March 2019 21:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff

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

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


[Kernel-packages] [Bug 1820310] Re: linux-gcp: 5.0.0-1001.1 -proposed tracker

2019-03-23 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
- phase: Promote to Proposed
- phase-changed: Wednesday, 20. March 2019 12:04 UTC
+ phase: Testing
+ phase-changed: Saturday, 23. March 2019 21:03 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Stalled -- packages no longer available
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 5.0.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Disco:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1819759
  phase: Testing
  phase-changed: Saturday, 23. March 2019 21:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)

2019-03-23 Thread Matheus
Okay, forget what I said, I just randomly run into the freeze with the
the -43 version after 3 hibernation cycles, Ill be testing with -42
now

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

Title:
  s2disk freezes at saving image to disk (hibernation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1
  hibernation was working flawlessly on my machine. (with kernel
  4.15-46! not a kernel issue then?)

  Another thing that got updated recently was nvidia drivers which were
  known to cause hibernation issues, but those were on restoring the
  snapshot.

  http://imgur.com/gallery/jOyHEcL  --> I get stuck on this screen after
  running hibernate or pm-hibernate. (sys-req REISUB combination works
  there and is the only good way to restart I found)

  
  SPECS

  Laptop Dell Inspiron 7567 A30P
  Intel Core i7-7700HQ
  1x 16 GB DDR4 
  1 TB HDD + 256 GB SSD 
  Nvidia GeForce GTX 1050 
  Ti FHD display 
  Intel Dual Band Wireless AC 3165 
  1x1 Motherboard: 
  Intel HM175 Graphics adapter: 
  NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, 
  Core: 1620 MHz, 
  Memory: 1752 MHz, 
  GDDR5, 21.21.13.7320 (ForceWare 373.20), 
  Nvidia Optimus

  nvidia driver: 415.27

  INFO

  # uname -a
  Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed 
Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  # free -m
totalusedfree  shared  buff/cache   
available
  Mem:  1590629258742 1614238   
12485
  Swap: 16333   0   16333

  # cat /etc/fstab | grep swap
  # swap was on /dev/sda8 during installation
  UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw  
0   0
  n

  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernate 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hiber 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep s2disk
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernation

  
  I could find nothing scrolling up on syslog about the hibernation process or 
with grep 

  
  An interesting Note is that if I run hibernate just after I boot, it works 
and resumes perfectly! But after some system usage it randomly has that problem 
if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 
once.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   matheus   25949 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matheus   25949 F...m pulseaudio
   /dev/snd/controlC0:  matheus   25949 F pulseaudio
   /dev/snd/seq:matheus4986 f qsynth
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06
  InstallationDate: Installed on 2018-05-10 (308 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug 
no_console_suspend systemd.log_level=info nvidia-drm.modeset=0
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)

2019-03-23 Thread Matheus
Ok so after running the right command to install the older kernel:

apt-get install linux-image-4.15.0-44-generic linux-headers-4.15.0-44
linux-headers-4.15.0-44-generic linux-modules-extra-4.15.0-44

Also tested with -42 and -43 versions, Hibernation worked just like
before with 4.15.0-43. So We can state this is a kernel bug since kernel
4.15.0-44, since with the -46, -45, -44 versions it doesn't work. It
also worked on the -42 version.

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

Title:
  s2disk freezes at saving image to disk (hibernation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1
  hibernation was working flawlessly on my machine. (with kernel
  4.15-46! not a kernel issue then?)

  Another thing that got updated recently was nvidia drivers which were
  known to cause hibernation issues, but those were on restoring the
  snapshot.

  http://imgur.com/gallery/jOyHEcL  --> I get stuck on this screen after
  running hibernate or pm-hibernate. (sys-req REISUB combination works
  there and is the only good way to restart I found)

  
  SPECS

  Laptop Dell Inspiron 7567 A30P
  Intel Core i7-7700HQ
  1x 16 GB DDR4 
  1 TB HDD + 256 GB SSD 
  Nvidia GeForce GTX 1050 
  Ti FHD display 
  Intel Dual Band Wireless AC 3165 
  1x1 Motherboard: 
  Intel HM175 Graphics adapter: 
  NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, 
  Core: 1620 MHz, 
  Memory: 1752 MHz, 
  GDDR5, 21.21.13.7320 (ForceWare 373.20), 
  Nvidia Optimus

  nvidia driver: 415.27

  INFO

  # uname -a
  Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed 
Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  # free -m
totalusedfree  shared  buff/cache   
available
  Mem:  1590629258742 1614238   
12485
  Swap: 16333   0   16333

  # cat /etc/fstab | grep swap
  # swap was on /dev/sda8 during installation
  UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw  
0   0
  n

  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernate 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hiber 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep s2disk
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernation

  
  I could find nothing scrolling up on syslog about the hibernation process or 
with grep 

  
  An interesting Note is that if I run hibernate just after I boot, it works 
and resumes perfectly! But after some system usage it randomly has that problem 
if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 
once.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   matheus   25949 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matheus   25949 F...m pulseaudio
   /dev/snd/controlC0:  matheus   25949 F pulseaudio
   /dev/snd/seq:matheus4986 f qsynth
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06
  InstallationDate: Installed on 2018-05-10 (308 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug 
no_console_suspend systemd.log_level=info nvidia-drm.modeset=0
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.sys.vendor: Dell Inc.


[Kernel-packages] [Bug 1821466] [NEW] Kernel 4.4.0-143 faulty

2019-03-23 Thread nob0dy
Public bug reported:

Since kernel update to 4.4.0-143, Oracle Virtualbox machines does not run 
anymore:
http://cb3hn.dyndns.tv/tmp/virtualbox_5.2.26.png
http://cb3hn.dyndns.tv/tmp/vboxconfig.png

Regards...

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1821466

Title:
  Kernel 4.4.0-143 faulty

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since kernel update to 4.4.0-143, Oracle Virtualbox machines does not run 
anymore:
  http://cb3hn.dyndns.tv/tmp/virtualbox_5.2.26.png
  http://cb3hn.dyndns.tv/tmp/vboxconfig.png

  Regards...

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

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


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

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

apport-collect 1821466

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

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

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

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

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

Title:
  Kernel 4.4.0-143 faulty

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since kernel update to 4.4.0-143, Oracle Virtualbox machines does not run 
anymore:
  http://cb3hn.dyndns.tv/tmp/virtualbox_5.2.26.png
  http://cb3hn.dyndns.tv/tmp/vboxconfig.png

  Regards...

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

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


[Kernel-packages] [Bug 1769792] Re: Keyboard and Touchpad do not work after suspend/resume

2019-03-23 Thread quique
Right now it seems the problem is still alive.
I’m using xubuntu 18.04:
Linux Kernel 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 
x86_64 GNU/Linux
on a Sony VAIO Laptop:
SVE1512E1EW (54512264)
Sony Corporation
version: C10FMXTT
serie: 54512264-0010407

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

Title:
  Keyboard and Touchpad do not work after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop is a Toshiba Satellite C850D with updated 18.04 installed.
  When resuming from suspend, I have no keyboard and touchpad.
  dmesg shows "i8042: Can't reactivate KBD port"

  This looks like a recurring problem, and is just like these:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014240
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1142118

  Here's the dmesg output from before and after suspending.
  https://paste.ubuntu.com/p/rsFX9Yw7Xh/

  This post also talks about this bit failing for a lot of people!
  http://lightrush.ndoytchev.com/random-1/i8042quirkoptions

  Some of the function keys work, such as changing the screen
  brightness, but the key (fn+F5) does not turn the touchpad back on. I
  have not yet tried any of the suggested options, as results have been
  mixed, but I will.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  7 22:01:26 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake

2019-03-23 Thread Kai-Heng Feng
Download them to a directory, cd to the directory, then run 
$ sudo dpkg -i *.deb

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

Title:
  Wifi + bluetooth adapters are gone after sleep/wake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the only fix I found was to power down and power back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uri2238 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 11:15:43 2019
  HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5
  InstallationDate: Installed on 2018-01-13 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF: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/1813537/+subscriptions

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


[Kernel-packages] [Bug 1821053] Re: [disco] [5.0.0-7.8] can't mount guest cifs share

2019-03-23 Thread Andreas Hasenack
Extra patch to be applied on top:

https://lore.kernel.org/linux-
cifs/cah2r5ms_md9uosm5x0acamtz2zhiu0+hvvzzjf2pgzqyxny...@mail.gmail.com/

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

Title:
  [disco] [5.0.0-7.8] can't mount guest cifs share

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  with a simple smb.conf setup like this:
  [pub]
  path = /pub
  guest ok = yes

  The following mount command fails when the running kernel is 5.0.0-7:
  root@ubuntu:~# dmesg -C
  root@ubuntu:~# mount //localhost/pub /mnt -o guest
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  root@ubuntu:~# dmesg
  [  178.469307] CIFS: Attempting to mount //localhost/pub
  [  178.469343] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.
  [  178.481741] CIFS VFS: failed to connect to IPC (rc=-13)
  [  178.485272] CIFS VFS: cifs_mount failed w/return code = -13

  samba server logs, in debug 5, show:
  [2019/03/20 17:25:19.365445,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.365524,  0] ../../lib/util/util.c:508(dump_data)
[] A6 62 5F 50 9C D7 31 42   14 34 52 9F AA 49 C8 31   .b_P..1B .4R..I.1
  [2019/03/20 17:25:19.365562,  0] ../../lib/util/util.c:508(dump_data)
[] 31 37 12 A2 D5 D4 59 99   0B 63 C5 21 EB 86 70 74   17Y. .c.!..pt
  [2019/03/20 17:25:19.369055,  0] 
../../libcli/smb/smb2_signing.c:169(smb2_signing_check_pdu)
Bad SMB2 signature for message
  [2019/03/20 17:25:19.369092,  0] ../../lib/util/util.c:508(dump_data)
[] 23 2C 4F 10 0E 4E 46 2E   8A 5B E3 70 0F B3 D3 FB   #,O..NF. .[.p
  [2019/03/20 17:25:19.369120,  0] ../../lib/util/util.c:508(dump_data)
[] 50 F7 C6 8A 6E BC B2 B7   1C 2F 43 30 90 6A 25 CA   P...n... ./C0.j%.

  
  With kernel 4.19.0-12-generic, the exact same system, the command works:

  root@ubuntu:~# dmesg -C

  root@ubuntu:~# mount //localhost/pub /mnt -o guest

  root@ubuntu:~# dmesg
  [  277.745885] FS-Cache: Loaded
  [  277.768408] FS-Cache: Netfs 'cifs' registered for caching
  [  277.768495] Key type cifs.spnego registered
  [  277.768498] Key type cifs.idmap registered
  [  277.768707] No dialect specified on mount. Default has changed to a more 
secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less 
secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) 
specify vers=1.0 on mount.

  root@ubuntu:~# mount -t cifs
  //localhost/pub on /mnt type cifs 
(rw,relatime,vers=default,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  root@ubuntu:~# uname -r
  4.19.0-12-generic

  
  Just looking at the list of patches queued up for the next upstream kernel 
release, at 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0,
 this one looks promising:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.0/cifs-do-not-skip-smb2-message-ids-on-send-failures.patch


  I can easily test a new kernel for you.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 18:04 seq
   crw-rw 1 root audio 116, 33 Mar 20 18:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  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
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=PARTUUID=e2b8e290-77c5-437c-a78d-b59424881b58 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UnreportableReason: This report is 

[Kernel-packages] [Bug 1819028] Re: Intel 9260 WiFi adapter doesn't work on B450 motherboard

2019-03-23 Thread bionicle159
I used Ukuu to update to 5.1-rc1, the integrated WiFi still doesn't work

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

Title:
  Intel 9260 WiFi adapter doesn't work on B450 motherboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, I know this has been a well discussed issue on Linux forums, but I
  am having extreme issues maintaining the built-in Intel WiFi in my
  motherboard, it resets everytime I update my distros (Ubuntu 18.04 and
  Linux Mint Cinnamon 18.3). My best fix for it is following the guide
  at [https://askubuntu.com/questions/1038242/no-wifi-option-on-
  ubuntu-18-04-and-16-04].

  I am wanting to know if there is a way to make this process more streamlined 
for users as this affects many and is a hassle to maintain properly. I know 
this has been addressed before with Ryzen CPUs but this shouldn't have to be 
necessary if the driver is baked into the kernel as this is quite frustrating 
for any user to go through, as it requires what is causing the problem to fix - 
a network connection. I don't mind if it's simpler to have a on/off feature 
like the Nvidia drivers have, as that is still a lot simpler than writing out a 
paragraphs of code.
   
  TL;DR I'm asking if changes could be added so that instead of needing a 
network connection (something that you can't have if the driver isn't built 
into/available through the distro) and writing a dissertation of code, they 
have a driver automatically work or a switch option like Broadcom and Nvidia 
have in this photo 
[https://linuxhint.com/wp-content/uploads/2017/11/driver-manager-1.png]

  I was referred here by the Linux Mint forum, please refer to the page
  in case any questions have already been answered there
  
[https://forums.linuxmint.com/viewtopic.php?f=49=289358=1=unread#unread]

  My system is a AMD Ryzen 2700x B450 with built-in Intel 9260 WiFi,
  Linux Mint 18.3/Ubuntu 18.04 dual boot.

  Thanks, Bionicle159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amir   2179 F pulseaudio
   /dev/snd/controlC1:  amir   2179 F pulseaudio
   /dev/snd/controlC2:  amir   2179 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b
  InstallationDate: Installed on 2018-08-22 (210 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Micro-Star International Co., Ltd. MS-7B85
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=4c3c212e-59c3-4de8-a1a2-24acc6e040d6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.157.21
  Tags:  sylvia
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450 GAMING PRO CARBON AC (MS-7B85)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd08/06/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B85:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450GAMINGPROCARBONAC(MS-7B85):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B85
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amir   2179 F pulseaudio
   /dev/snd/controlC1:  amir   2179 F pulseaudio
   /dev/snd/controlC2:  amir   2179 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=7575ec42-19af-4131-8368-b69700abca9b
  InstallationDate: Installed on 2018-08-22 (210 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Micro-Star International Co., Ltd. MS-7B85
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2019-03-23 Thread Michael Lazin
I am running ubuntu 18.04 and using the low latency kernel rather than
the default kernel.  Since the "upgrade" to nvidia 390 it looks like the
kernel module is actually missing from my filesystem.  Running dmesg |
grep nvidia and modprobe | grep nvidia tells me the nvidia driver is not
loaded.  When I try to load it with modprobe it's not in the proper path
so it can't load.  I tried reverting the nvidia driver and the kernel
but the kernel module is still mysteriously missing.  I'm going to
reinstall with ubuntu studio 18.10 because this update has basically
destroyed the functionality of my desktop.  I need 1920x1068 resolution
and that's not an option with the xrandr command without the nvidia
driver.  I did not check to see of nouveau was loaded as a kernel
module, I just gotta reinstall.  I hope this helps someone.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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


[Kernel-packages] [Bug 1496942] Re: Infiniband (mellanox) SR-IOV and libvirt + libnl problems

2019-03-23 Thread Matija Marinic
** Also affects: linux (Debian)
   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/1496942

Title:
  Infiniband (mellanox) SR-IOV and libvirt + libnl problems

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  When trying to start an IB SR-IOV guest by using the following XML:

  


  


  

  following the Mellanox SR-IOV guide, we are able to start guests using
  kernel 3.16 (Utopic).

  We are NOT able to start guests using 3.13 OR 3.19. The following
  error occurs:

  2015-09-17 02:25:07.208+: 52157: info : libvirt version: 1.2.12, package: 
1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:07.208+: 52157: error : virSecurityDriverLookup:80 : 
unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:42.308+: 52281: info : libvirt version: 1.2.12, package: 
1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:42.308+: 52281: error : virSecurityDriverLookup:80 : 
unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:48.996+: 52274: error : virNetDevParseVfConfig:1905 : 
internal error: missing IFLA_VF_INFO in netlink response
  2015-09-17 02:25:49.006+: 52274: error : virFileReadAll:1347 : Failed to 
open file '/var/run/libvirt/hostdevmgr/ib0_vf0': No such file or directory
  2015-09-17 02:25:49.006+: 52274: error : virFileReadAll:1347 : Failed to 
open file '/var/run/libvirt/qemu/ib0_vf0': No such file or directory

  So probably there is some regression in between 3.16 and 3.19 for the
  IFLA_VF_INFO feature from netlink AND this has to be backported to
  kernel 3.13 for Trusty to have IB SR-IOV working.

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

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


[Kernel-packages] [Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

2019-03-23 Thread Valentin Manea
Can't do apport when the crash happens, I get the logs from efi-pstore.

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

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

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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


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

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

apport-collect 1821434

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: 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/1821434

Title:
  Panic on suspend/resume Kernel panic - not syncing: stack-protector:
  Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:

  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
  <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)

  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
  22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)

  
  When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

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


[Kernel-packages] [Bug 1821434] [NEW] Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40

2019-03-23 Thread Valentin Manea
Public bug reported:

With efi-pstore activated I get the following panic in Linux 4.15.0-46
after resume:

<6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
<6>[12007.593469] ata10.02: hard resetting link
<6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
<6>[12007.911149] ata10.00: configured for UDMA/133
<0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack is 
corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
<0>[12007.972508]
<4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
<4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
<4>[12007.972518] Call Trace:
<4>[12007.972525]  dump_stack+0x63/0x8b
<4>[12007.972530]  panic+0xe4/0x244
<4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
<4>[12007.972536]  __stack_chk_fail+0x19/0x20
<4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
<4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
<4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
<4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
<4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
<4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
<4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
<4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
<4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
<4>[12007.972559]  ata_scsi_error+0x95/0xd0
<4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
<4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
<4>[12007.972566]  kthread+0x121/0x140
<4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
<4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
<4>[12007.972572]  ret_from_fork+0x22/0x40
<0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 (relocation 
range: 0x8000-0xbfff)

I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller 
(rev 02)


When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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

** Description changed:

  With efi-pstore activated I get the following panic in Linux 4.15.0-46
  after resume:
  
  <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330)
  <6>[12007.593469] ata10.02: hard resetting link
  <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330)
  <6>[12007.911149] ata10.00: configured for UDMA/133
  <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack 
is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
- <0>[12007.972508] 
+ <0>[12007.972508]
  <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P   OE
4.15.0-46-generic #49-Ubuntu
  <4>[12007.972517] Hardware name: System manufacturer System Product 
Name/A320M-C, BIOS 1001 12/10/2017
  <4>[12007.972518] Call Trace:
  <4>[12007.972525]  dump_stack+0x63/0x8b
  <4>[12007.972530]  panic+0xe4/0x244
  <4>[12007.972533]  ? sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972536]  __stack_chk_fail+0x19/0x20
  <4>[12007.972538]  sata_pmp_eh_recover+0xa2b/0xa40
  <4>[12007.972543]  ? ahci_do_softreset+0x260/0x260 [libahci]
  <4>[12007.972545]  ? ahci_do_hardreset+0x140/0x140 [libahci]
  <4>[12007.972547]  ? ata_phys_link_offline+0x60/0x60
  <4>[12007.972549]  ? ahci_stop_engine+0xc0/0xc0 [libahci]
  <4>[12007.972552]  sata_pmp_error_handler+0x22/0x30
  <4>[12007.972554]  ahci_error_handler+0x45/0x80 [libahci]
  <4>[12007.972556]  ata_scsi_port_error_handler+0x29b/0x770
  <4>[12007.972558]  ? ata_scsi_cmd_error_handler+0x101/0x140
  <4>[12007.972559]  ata_scsi_error+0x95/0xd0
  <4>[12007.972562]  ? scsi_try_target_reset+0x90/0x90
  <4>[12007.972563]  scsi_error_handler+0xd0/0x5b0
  <4>[12007.972566]  kthread+0x121/0x140
  <4>[12007.972567]  ? scsi_eh_get_sense+0x200/0x200
  <4>[12007.972569]  ? kthread_create_worker_on_cpu+0x70/0x70
  <4>[12007.972572]  ret_from_fork+0x22/0x40
  <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 
(relocation range: 0x8000-0xbfff)
  
  I have also tried 4.18 and 4.20 from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The 
problem seems to be related to an add-on PCI-E SATA card:
- 24:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge 
(rev 04)
+ 22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA 
Controller (rev 02)
  
- When disks are connected to the card port -> panic, no disks connected
- -> no panic.
+ 
+ When disks are connected to the card port -> panic, no disks connected -> no 
panic.

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