date:20180608

Launchpad has imported 29 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=69131.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2014-01-21T11:15:48+00:00 adi wrote:

Hi!

As of 3.13, the wifi card on my HP nx6325 remains hard-blocked no matter
how much I press the hardware button or run rfkill:

Oddly enough, it reports hard-blocked after trying to set the interface
up.

Transcript:

chopin:~# rfkill list
2: phy2: Wireless LAN
Soft blocked: no
Hard blocked: yes
chopin:~# rmmod b43
chopin:~# modprobe b43
chopin:~# rfkill list
3: phy3: Wireless LAN
Soft blocked: no
Hard blocked: no
chopin:~# ifconfig wlan0 up
chopin:~# iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down

chopin:~# rfkill list
3: phy3: Wireless LAN
Soft blocked: no
Hard blocked: yes
--- end of transcript ---

The LED remains off all the time, it only flashes once when running
"ifconfig wlan0 up", but the device isn't really up.


Needless to say it's impossible to connect via wifi, hence the raised priority.

For the sake of completeness, let me add that 3.12.8 isn't affected, so
it's clearly a regression.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/0


On 2014-01-21T11:31:30+00:00 mjg59-kernel wrote:

Does rfkill list show an hp-wmi entry on 3.12?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/1


On 2014-01-21T13:02:46+00:00 adi wrote:

Yes, it does:

chopin:~# uname -a
Linux chopin 3.12.8 #2 SMP PREEMPT Tue Jan 21 13:42:16 CET 2014 x86_64 GNU/Linux
chopin:~# rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
2: hp-gps: GPS
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/2


On 2014-01-21T13:27:34+00:00 mjg59-kernel wrote:

Can you try reverting 997daa1bd9aca412ab97955a35b26c460c0ec7a4 and see
if that helps?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/3


On 2014-01-21T14:09:17+00:00 adi wrote:

This really helps. With 997daa1bd9aca412ab97955a35b26c460c0ec7a4
reverted, it works again:

chopin:~# uname -a
Linux chopin 3.13.0 #2 SMP PREEMPT Tue Jan 21 14:51:15 CET 2014 x86_64 GNU/Linux
chopin:~# rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: hp-gps: GPS
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no


I took the liberty to attach the acpidump output of the machine in question, 
just in case you need to have a look at the WMI section.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/4


On 2014-01-21T14:09:43+00:00 adi wrote:

Created attachment 122891
acpidump output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/5


On 2014-01-21T14:54:59+00:00 mjg59-kernel wrote:

Created attachment 122901
Test patch

Ok. Can you reapply that commit and then test this patch?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/6


On 2014-01-21T15:12:50+00:00 adi wrote:

Your patch works like a charm:

chopin:~# uname -a
Linux chopin 3.13.0 #3 SMP PREEMPT Tue Jan 21 16:06:03 CET 2014 x86_64 GNU/Linux
chopin:~# rfkill list
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: hp-gps: GPS
Soft blocked: yes
Hard blocked: yes
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no


JFTR, hp_wmi_bios_2009_later is unused for now:

drivers/platform/x86/hp-wmi.c:296:12: warning: ‘hp_wmi_bios_2009_later’ defined 
but not used [-Wunused-function]
 static int hp_wmi_bios_2009_later(void)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290418/comments/7

[Kernel-packages] [Bug 1775526] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned

2018-06-08 Thread jamso

I had the exact same issue. It actual problem is stated here by someone
else, with a solution:

https://devtalk.nvidia.com/default/topic/1036167/linux/stuck-trying-to-
intall-nvidia-390-ubuntu-18-04-lts-/

The problem is a dialogue requesting to set a password (for secureboot
stuff) never pops up. I think the password must be 8 or more characters
(not sure if there's an upper limit).

A workaround given was when the update gets stuck, type a password in
the terminal blindly and press return twice (using the same password
both times). This worked for me, except I had to type the password in
about 4 times. (This is not necessary in theory, but I think maybe
you're supposed to press "return" at other occasions to pass "ok"
checkpoints. Therefore, you have to type the password unnecessarily and
press return because you don't know where the checkpoints are.)

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

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: installed linux-image-4.15.0-22-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Failed to build package when installing nvidia drivers. Every time
  `Building initial module for 4.15.0-22-generic` is stuck. There is no
  antivirus on my machine.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: rfcomm bnep nouveau asus_nb_wmi asus_wmi sparse_keymap 
mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core ath3k btusb btrtl ath9k ath9k_common btbcm ath9k_hw 
uvcvideo btintel bluetooth videobuf2_vmalloc videobuf2_memops ath 
videobuf2_v4l2 videobuf2_core mac80211 videodev media mei_me mei rtsx_pci_ms 
memstick intel_cstate intel_rapl_perf cfg80211 shpchp lpc_ich ie31200_edac wmi 
mac_hid asus_wireless i915 rtsx_pci_sdmmc r8169 rtsx_pci
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Jun  7 12:36:23 2018
  ErrorMessage: installed linux-image-4.15.0-22-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345

2018-06-08 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1775527

Title:
  Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test
  running after a day #345

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

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2016-09-08 15:01:30 
==
  We have installed 16.04.1 on our guest and running IO stress test against via 
virtual qlogic disk. After running around 8 hrs, this error popping up 
"xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these 
errors "xfs_log_force: error -5 returned" fill up all the log.

  Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error: 
block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32
  Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp: 
xfs_trans_read_buf() returned error -5.
  Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9): 
xfs_do_force_shutdown(0x8) called from line 3433 of file 
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address = 
0xd37951f4
  Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error: 
block 0x703d54 ("xlog_iodone") error 5 numblks 64
  Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9): 
xfs_do_force_shutdown(0x2) called from line 1197 of file 
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address = 
0xd37a4c00
  Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error 
Detected. Shutting down filesystem
  Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the 
filesystem and rectify the problem(s)

  follow with all of these error that quickly fill up dmesg log
  Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2 
file system using the ext4 subsystem
  Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted 
filesystem without journal. Opts: (null)
  Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed
  Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force: 
error -5 returned.
  Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force: 
error -5 returned.

  == Comment: #1 - Chanh H. Nguyen  - 2016-09-08 15:02:27 
==
  We recently re-created this bug on our new system "cressg2" which is using a 
different SAN on kernel -36. 
  My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test, 
and it is hitting "xfs_log_force: error -5 returned"  problem after it runs the 
tests for 15 hours. It is using our lab storage (SVC SAN storage configuation 
with access to DS8000 Volume) and switch, compare to tinyg3, so it is using 
different storage and fabric switch. 

  root@cressg2:~# uname -a
  Linux cressg2 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  [Wed Sep  7 10:26:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:32 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:49 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:27:56 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:28:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:28:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
  [Wed Sep  7 10:29:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.

[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux: 3.13.0-151.201 -proposed tracker

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

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

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

  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1774764] Re: linux-oem: 4.15.0-1008.11 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-oem: 4.15.0-1008.11 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G

2018-06-08 Thread Peter Silva

OK did that. the crash is a little different.

** Attachment added: "IMG_20180608_185330.jpg"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+attachment/5150431/+files/IMG_20180608_185330.jpg

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

Title:
Cannot boot/install AMD Ryzen 2400G

Status in linux package in Ubuntu:
Confirmed

Bug description:
Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years
or so. Now it only runs windows (same hardware fresh installs windows with no
issue). brand new ryzen 2nd gen with graphics.

I know about graphics drivers issues, wasn't expecting that to be dealt with.
Just trying to use it as a cpu. So I put in an older (RADEON HD 7850
pitcairn) video card to get some functionality.

Without the video card, it boots, but the display is unusable. I can
ssh in and see that it works fine as a server, but cannot use terminal
or graphical display.

With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu",
and it goes into an infinite loop. photo attached. I tried 16.04.4 and
I think it just went into a blank screen.

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

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

[Kernel-packages] [Bug 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-gcp: 4.13.0-1019.23 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux: 4.13.0-45.50 -proposed tracker

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

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

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

  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1775855] Re: Unable to deploy Bionic ppc64le on P8 systems (kernel-panic)

2018-06-08 Thread Kleber Sacilotto de Souza

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

This is the same issue as reported on bug 1773162.

** This bug has been marked a duplicate of bug 1773162
   4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec 
supported)

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

Title:
  Unable to deploy Bionic ppc64le on P8 systems (kernel-panic)

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

Bug description:
  I can't deploy Bioinc on the P8 system "modoc", it will run into a
  kernel-panic situation (power9 system works fine).

  From the test history, this P8 node was tested with 4.15.0-21, which
  mean that the deployment works with some version earlier than
  4.15.0-21, and at least it can boot with 4.15.0-21 in the last cycle.

  So it's a bit odd to me to see the deployment failure here, as it should
  be deployed with working 4.15.0-21 from the last cycle.

  And it's not the 4.15.0-23 in -proposed that's causing this this problem, the 
system was never boot with 4.15.0-21.
   
  + /var/lib/jenkins/kernel-testing/metal --debug --nc --series=bionic 
--arch=ppc64el --flavour=generic --required-kernel-version=4.15.0-23.25 
--pkg-name=None modoc
   . Provisioner setup
  Releasing...   
  Allocating...   
  Deploying...   
  Traceback (most recent call last):
File "/var/lib/jenkins/kernel-testing/metal", line 212, in 
  exit(app.main(args))
File "/var/lib/jenkins/kernel-testing/metal", line 101, in main
  if metal.provision():
File "/var/lib/jenkins/kernel-testing/lib/provisioning.py", line 837, in 
provision
  if not s.ps.provision():
File "/var/lib/jenkins/kernel-testing/lib/provisioning.py", line 66, in 
provision
  retval = s.server.provision()
File "/var/lib/jenkins/kernel-testing/lib/maas.py", line 250, in provision
  s.deploy(s.hostname, s.series, s.arch)
File "/var/lib/jenkins/kernel-testing/lib/maas.py", line 241, in deploy
  raise MachineDeploymentTimeout('The specified timeout (%d) was reached 
while waiting for the system (%s) to be deployed.' % ((timeout * 60), hostname))
  lib.maas.MachineDeploymentTimeout: The specified timeout (108000) was reached 
while waiting for the system (modoc) to be deployed.

  Output from IPMI console:
  [1.910940] Loaded X.509 cert 'Build time autogenerated kernel key: 
c68a20e7bfd228430401173121559235d0c5ceb1'
  [1.911145] zswap: loaded using pool lzo/zbud
  [1.911370] Bad kernel stack pointer 7fffd1751cf0 at c000b9ec
  [1.911429] Oops: Bad kernel stack pointer, sig: 6 [#7]
  [1.911475] LE SMP NR_CPUS=2048 NUMA PowerNV
  [1.911522] Modules linked in:
  [1.911557] CPU: 39 PID: 1218 Comm: modprobe Tainted: G  D  
4.15.0-22-generic #24-Ubuntu
  [1.911637] NIP:  c000b9ec LR:  CTR: 

  [1.911706] REGS: c0003fe2bd40 TRAP: 0380   Tainted: G  D  
 (4.15.0-22-generic)
  [1.911785] MSR:  90001031   CR:   XER: 

  [1.911856] CFAR: c000b934 SOFTE: -4611686018403131680
  [1.911856] GPR00:  7fffd1751cf0  

  [1.911856] GPR04:    

  [1.911856] GPR08:    

  [1.911856] GPR12: 7ef5a4501700 90001000  

  [1.911856] GPR16:    

  [1.911856] GPR20:    

  [1.911856] GPR24:    

  [1.911856] GPR28:    

  [1.912418] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [1.912424] LR []   (null)
  [1.912429] Call Trace:
  [1.912442] Instruction dump:
  [1.912476] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090
  [1.912547] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 4810
  [1.912619] ---[ end trace 44c2744c93d781cc ]---

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

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

2018-06-08 Thread Tiago Stürmer Daitx

IcedTea 2.6.14 has backported a fix for the exec guard issue and will be
available in Trusty's openjdk-7 version 7u181-2.6.14-0ubuntu0.1.

The fix for OpenJDK-8 will be included in the next security update.

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Artful:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux-oem: 4.13.0-1030.33 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

2018-06-08 Thread Dimitri John Ledkov

I think this is actually fine. Ship it.

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

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

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

[Kernel-packages] [Bug 1775326] Re: The kernel NULL pointer dereference happens when accessing the task_struct by task_cpu() in function cpuacct_charge()

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  The kernel NULL pointer dereference happens when accessing the
  task_struct by task_cpu() in function cpuacct_charge()

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

Bug description:
  [Impact]

  In function cpuacct_charge(), the NULL pointer dereference happens
  with the stack pointer being zero inside the task_struct when the
  task_cpu() is trying to access the member CPU of the struct
  thread_info inside the stack. It's a use-after-free corruption
  happening in the situation that the task_struct is released almost
  concurrently before accessing the task_struct->stack.

  void cpuacct_charge(struct task_struct *tsk, u64 cputime)
   {
  struct cpuacct *ca;
  int cpu;
   
  cpu = task_cpu(tsk);
   
  rcu_read_lock();
   
  ca = task_ca(tsk);
   
  while (true) {
  u64 *cpuusage = per_cpu_ptr(ca->cpuusage, cpu);
  *cpuusage += cputime;
   
  ca = parent_ca(ca);
  if (!ca)
  break;
  }

rcu_read_unlock();
  }

  
  BUG: unable to handle kernel NULL pointer dereference at 0010
  IP: [] cpuacct_charge+0x14/0x40
  PGD 0 
  Oops:  [#1] SMP  
  CPU: 10 PID: 148614 Comm: qemu-system-x86 Tainted: PW  OE   
4.4.0-45-generic #66~14.04.1-Ubuntu
  Hardware name: Dell Inc. PowerEdge R630/02C2CP, BIOS 2.1.7 06/16/2016
  task: 881ff0f01b80 ti: 88018fd7 task.ti: 88018fd7
  RIP: 0010:[]  [] cpuacct_charge+0x14/0x40
  RSP: 0018:88018fd73d10  EFLAGS: 00010246
  RAX:  RBX: 8801931e8000 RCX: 88010caff200
  RDX: 880124508000 RSI: 0066f757398831d6 RDI: 8801931e7fa0
  RBP: 88018fd73d10 R08: c04b8320 R09: 0001
  R10: 0001 R11:  R12: 0066f757398831d6
  R13: 0066f757398b8997 R14: 8801931e7fa0 R15: 0001
  FS:  7f162aaf7700() GS:881ffe74() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0010 CR3: 00011d86e000 CR4: 003426e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88018fd73d28 810b1a9f 8801931e8000 88018fd73d40
   c069df72 8801931e8000 88018fd73da8 c069f121
   881ff0f01b80  881ff0f01b80 810bddc0
  Call Trace:
   [] update_curr+0xdf/0x170
   [] kvm_vcpu_check_block+0x12/0x60 [kvm]
   [] kvm_vcpu_block+0x191/0x2d0 [kvm]
   [] ? prepare_to_wait_event+0xf0/0xf0
   [] kvm_arch_vcpu_ioctl_run+0x17e/0x3d0 [kvm]
   [] kvm_vcpu_ioctl+0x2ab/0x640 [kvm]
   [] ? perf_event_context_sched_in+0x87/0xa0
   [] do_vfs_ioctl+0x2dd/0x4c0
   [] ? __audit_syscall_entry+0xaf/0x100
   [] ? do_audit_syscall_entry+0x66/0x70
   [] SyS_ioctl+0x79/0x90
   [] entry_SYSCALL_64_fastpath+0x16/0x75
  Code: 9a 11 00 5b 48 c7 c0 f4 ff ff ff 5d eb df 66 0f 1f 84 00 00 00 00 00 0f 
1f 44 00 00 55 48 8b 47 08 48 8b 97 78 07 00 00 48 89 e5 <48> 63 48 10 48 8b 52 
60 48 8b 82 b8 00 00 00 48 03 04 cd c0 7a
  RIP  [] cpuacct_charge+0x14/0x40
   RSP 
  CR2: 0010
  ---[ end trace 419a30375d0e4622 ]---


  [Fix]

  The patch uses this_cpu_ptr() instead of getting the CPU number by 
  task_cpu() and proceeds to get the cpu_usage by per_cpu_ptr(). And
  that can avoid accessing the thread_info inside the stack. 

  commit 73e6aafd9ea81498d31361f01db84a0118da2d1c
  Author: Zhao Lei 
  Date:   Thu Mar 17 12:19:43 2016 +0800

  sched/cpuacct: Simplify the cpuacct code
  
   - Use for() instead of while() loop in some functions
 to make the code simpler.
  
   - Use this_cpu_ptr() instead of per_cpu_ptr() to make the code
 cleaner and a bit faster.
  
  Suggested-by: Peter Zijlstra 
  Signed-off-by: Zhao Lei 
  Signed-off-by: Peter Zijlstra (Intel) 
  Cc: Linus Torvalds 
  Cc: Tejun Heo 
  Cc: Thomas Gleixner 
  Link: 
http://lkml.kernel.org/r/d8a7ef9592f55224630cb26dea239f05b6398a4e.1458187654.git.zhao...@cn.fujitsu.com
  Signed-off-by: Ingo Molnar 


  [Test]
  The test kernel has been tested by the Qemu and cannot be reproduced.

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

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

[Kernel-packages] [Bug 1775945] Re: Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid

2018-06-08 Thread Pieter Smith

O'h I forgot to mention it. After experiencing this problem, I tried a
fresh install. This did not resolve the issue.

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

Title:
  Lenovi X1 Carbon regularly has frozen lock- or dark screen after
  closing lid

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I was running ubuntu 17.10 for months with no issues. After upgrading to 
18.04, closing the lid regularly (but not always) results in either:
  1. The display staying on with a frozen lock-screen, or
  2. The display powered off, but the notebook still powered on. 

  In both cases the notebook does not respond. A five-second press of
  the power button to hard-reboot the computer is the only means of
  recovery.

  After powering the notebook back on, there are no files in /var/crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  9 00:00:48 2018
  InstallationDate: Installed on 2018-06-02 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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-signed/+bug/1775945/+subscriptions

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

[Kernel-packages] [Bug 1775945] [NEW] Lenovi X1 Carbon regularly has frozen lock- or dark screen after closing lid

2018-06-08 Thread Pieter Smith

Public bug reported:

I was running ubuntu 17.10 for months with no issues. After upgrading to 18.04, 
closing the lid regularly (but not always) results in either:
1. The display staying on with a frozen lock-screen, or
2. The display powered off, but the notebook still powered on. 

In both cases the notebook does not respond. A five-second press of the
power button to hard-reboot the computer is the only means of recovery.

After powering the notebook back on, there are no files in /var/crash.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  9 00:00:48 2018
InstallationDate: Installed on 2018-06-02 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Lenovi X1 Carbon regularly has frozen lock- or dark screen after
  closing lid

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I was running ubuntu 17.10 for months with no issues. After upgrading to 
18.04, closing the lid regularly (but not always) results in either:
  1. The display staying on with a frozen lock-screen, or
  2. The display powered off, but the notebook still powered on. 

  In both cases the notebook does not respond. A five-second press of
  the power button to hard-reboot the computer is the only means of
  recovery.

  After powering the notebook back on, there are no files in /var/crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  9 00:00:48 2018
  InstallationDate: Installed on 2018-06-02 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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-signed/+bug/1775945/+subscriptions

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

[Kernel-packages] [Bug 1758378] Re: [Hyper-V] PCI: hv: Fix 2 hang issues in hv_compose_msi_msg

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

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

Title:
  [Hyper-V] PCI: hv: Fix 2 hang issues in hv_compose_msi_msg

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Invalid

Bug description:
  We've identified some issues in recent testing against upstream 4.15
  SR-IOV and DPDK. The following commits are in Lorenzo's PCI tree on
  their way into 4.16 and stable:

  Tree:
  
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/log/?h=pci/hv

  PCI: hv: Only queue new work items in hv_pci_devices_present() if necessary
  If there is pending work in hv_pci_devices_present() we just need to add
  the new dr entry into the dr_list. Add a check to detect pending work
  items and update the code to skip queuing work if pending work items
  are detected.

  
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv=948373b3ed1bcf05a237c24675b84804315aff14

  PCI: hv: Remove the bogus test in hv_eject_device_work()
  When kernel is executing hv_eject_device_work(), hpdev->state value must
  be hv_pcichild_ejecting; any other value would consist in a bug,
  therefore replace the bogus check with an explicit WARN_ON() on the
  condition failure detection.

  
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv=fca288c0153b2b97114b9081bc3c33c3735145b6

  PCI: hv: Fix a comment typo in _hv_pcifront_read_config()
  Comment in _hv_pcifront_read_config() contains a typo, fix it.

  No functional change.

  
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv=df3f2159f4e4146d40b244725ce79ed921530b99

  PCI: hv: Fix 2 hang issues in hv_compose_msi_msg()
  1. With the patch "x86/vector/msi: Switch to global reservation mode",
  the recent v4.15 and newer kernels always hang for 1-vCPU Hyper-V VM
  with SR-IOV. This is because when we reach hv_compose_msi_msg() by
  request_irq() -> request_threaded_irq() ->__setup_irq()->irq_startup()
  -> __irq_startup() -> irq_domain_activate_irq() -> ... ->
  msi_domain_activate() -> ... -> hv_compose_msi_msg(), local irq is
  disabled in __setup_irq().

  Note: when we reach hv_compose_msi_msg() by another code path:
  pci_enable_msix_range() -> ... -> irq_domain_activate_irq() -> ... ->
  hv_compose_msi_msg(), local irq is not disabled.

  hv_compose_msi_msg() depends on an interrupt from the host.
  With interrupts disabled, a UP VM always hangs in the busy loop in
  the function, because the interrupt callback hv_pci_onchannelcallback()
  can not be called.

  We can do nothing but work it around by polling the channel. This
  is ugly, but we don't have any other choice.

  2. If the host is ejecting the VF device before we reach
  hv_compose_msi_msg(), in a UP VM, we can hang in hv_compose_msi_msg()
  forever, because at this time the host doesn't respond to the
  CREATE_INTERRUPT request. This issue exists the first day the
  pci-hyperv driver appears in the kernel.

  Luckily, this can also by worked around by polling the channel
  for the PCI_EJECT message and hpdev->state, and by checking the
  PCI vendor ID.

  Note: actually the above 2 issues also happen to a SMP VM, if
  "hbus->hdev->channel->target_cpu == smp_processor_id()" is true.

  
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv=de0aa7b2f97d348ba7d1e17a00744c989baa0cb6

  PCI: hv: Serialize the present and eject work items
  When we hot-remove the device, we first receive a PCI_EJECT message and
  then receive a PCI_BUS_RELATIONS message with bus_rel->device_count == 0.

  The first message is offloaded to hv_eject_device_work(), and the second
  is offloaded to pci_devices_present_work(). Both the paths can be running
  list_del(>list_entry), causing general protection fault, because
  system_wq can run them concurrently.

  The patch eliminates the race condition.

  Since access to present/eject work items is serialized, we do not need the
  hbus->enum_sem anymore, so remove it.

  
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv=021ad274d7dc31611d4f47f7dd4ac7a224526f30

  All 4.15-based kernels need these fixes, or any kernels that picked up:
  Fixes: 4900be83602b ("x86/vector/msi: Switch to global reservation mode")

  The race condition fixed by the serialization patch

[Kernel-packages] [Bug 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.

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

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

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

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

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

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

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

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

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

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

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

  Before Hotplug:

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

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  



  root@boslcp3:~#  

  6. After this operation, guest becomes unrepsonsive as below

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

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


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

  7. ping to

[Kernel-packages] [Bug 1775217] Re: bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360

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

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

Title:
  bluetooth controller fail after suspend with USB autosuspend on XPS 13
  9360

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

Bug description:
  == SRU Justification ==
  This is a regression introduced in v4.15 and Bionic.  The bluetooth
  controller fails after suspend with USB autosuspend on an XPS 13 9360.

  This regression is fixed by mainline commit 596b07a9a226.  This commit
  was also cc'd to upstream stable, but it has not landed in Bionic via
  stable updates as of yet.

  == Fix ==
  596b07a9a226 ("Bluetooth: btusb: Add Dell XPS 13 9360 to 
btusb_needs_reset_resume_table")

  == Regression Potential ==
  Low.  This patch has also been cc'd to upstream stable, so it recieved
  additonal 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.


  
  More information here: https://bugzilla.redhat.com/show_bug.cgi?id=1514836

  Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.22.23
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilhem2319 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 18:19:20 2018
  HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3
  InstallationDate: Installed on 2018-02-26 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet 
splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 
i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1774636] Re: Lenovo V330 needs patch in ideapad_laptop module for rfkill

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

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

Title:
  Lenovo V330 needs patch in ideapad_laptop module for rfkill

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

Bug description:
  == SRU Justification ==
  The quite new Lenovo V330 is not yet completely supported by the
  ideapad_laptop module. Without an explicit rule, this module assumes that
  a hardware kill switch for wireless devices exists and thus sometimes boots
  up with all devices hard blocked and no way to reenable them at runtime.

  This requested patch has been sent upstream, but it is not in mainline as of 
yet.
  Since this laptop is available now and the bug is a real blocker for
  unexperienced users, this patch is being request as SAUCE.

  == Fix ==
  UBUNTU: SAUCE: Add Lenovo V330 to the ideapad_laptop rfkill blacklist

  == Regression Potential ==
  Low.  This patch just adds an additon DMI entry.

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


  The quite new Lenovo V330 is not yet completely supported by the
  ideapad_laptop module. Without an explicit rule, this module assumes
  that a hardware kill switch for wireless devices exists and thus
  sometimes boots up with all devices hard blocked and no way to
  reenable them at runtime.

  I have provided a patch to the kernel developers upstream: 
https://bugzilla.kernel.org/show_bug.cgi?id=199855
  However, there is not much activity at the moment. Since this laptop is 
available now and the bug is a real blocker for unexperienced users, would it 
be possible to add the (quite simple) fix to the ubuntu kernel until it is 
accepted upstream?

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

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

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

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

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

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

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.

[Kernel-packages] [Bug 1775884] Re: Network installs fail on SocioNext board

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

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

Title:
  Network installs fail on SocioNext board

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

Bug description:
  [Impact]
  It is not possible to perform a network install over the onboard NIC.

  [Test Case]
  Perform a d-i network install.

  [Fix]
  There are fixes for this upstream that cleanly cherry-pick back to bionic's 
kernel.

  [Regression Risk]
  Fixes are restricted to the netsec driver that is only currently used for the 
NIC on this system.

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

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

[Kernel-packages] [Bug 1775771] Re: Xenial update to 4.4.134 stable release

2018-06-08 Thread Kleber Sacilotto de Souza

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

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

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

Title:
  Xenial update to 4.4.134 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree
     or a minimally backported form of that patch. The 4.4.134 upstream
     stable stable patch set is now available. It should be included
     in the Ubuntu kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.134 stable release shall be
     applied:

* Linux 4.4.134
* s390/ftrace: use expoline for indirect branches
* kdb: make "mdr" command repeat
* Bluetooth: btusb: Add device ID for RTL8822BE
* ASoC: samsung: i2s: Ensure the RCLK rate is properly determined
* regulator: of: Add a missing 'of_node_put()' in an error handling path of 
'of_regulator_match()'
* scsi: lpfc: Fix frequency of Release WQE CQEs
* scsi: lpfc: Fix soft lockup in lpfc worker thread during LIP testing
* scsi: lpfc: Fix issue_lip if link is disabled
* netlabel: If PF_INET6, check sk_buff ip header version
* selftests/net: fixes psock_fanout eBPF test case
* perf report: Fix memory corruption in --branch-history mode 
--branch-history
* perf tests: Use arch__compare_symbol_names to compare symbols
* x86/apic: Set up through-local-APIC mode on the boot CPU if 'noapic' 
specified
* drm/rockchip: Respect page offset for PRIME mmap calls
* MIPS: Octeon: Fix logging messages with spurious periods after newlines
* audit: return on memory error to avoid null pointer dereference
* crypto: sunxi-ss - Add MODULE_ALIAS to sun4i-ss
* clk: samsung: exynos3250: Fix PLL rates
* clk: samsung: exynos5250: Fix PLL rates
* clk: samsung: exynos5433: Fix PLL rates
* clk: samsung: exynos5260: Fix PLL rates
* clk: samsung: s3c2410: Fix PLL rates
* media: cx25821: prevent out-of-bounds read on array card
* udf: Provide saner default for invalid uid / gid
* PCI: Add function 1 DMA alias quirk for Marvell 88SE9220
* serial: arc_uart: Fix out-of-bounds access through DT alias
* serial: fsl_lpuart: Fix out-of-bounds access through DT alias
* serial: imx: Fix out-of-bounds access through serial port index
* serial: mxs-auart: Fix out-of-bounds access through serial port index
* serial: samsung: Fix out-of-bounds access through serial port index
* serial: xuartps: Fix out-of-bounds access through DT alias
* rtc: tx4939: avoid unintended sign extension on a 24 bit shift
* staging: rtl8192u: return -ENOMEM on failed allocation of priv->oldaddr
* hwrng: stm32 - add reset during probe
* enic: enable rq before updating rq descriptors
* clk: rockchip: Prevent calculating mmc phase if clock rate is zero
* media: em28xx: USB bulk packet size fix
* dmaengine: pl330: fix a race condition in case of threaded irqs
* media: s3c-camif: fix out-of-bounds array access
* media: cx23885: Set subdev host data to clk_freq pointer
* media: cx23885: Override 888 ImpactVCBe crystal frequency
* ALSA: vmaster: Propagate slave error
* x86/devicetree: Fix device IRQ settings in DT
* x86/devicetree: Initialize device tree before using it
* usb: gadget: composite: fix incorrect handling of OS desc requests
* usb: gadget: udc: change comparison to bitshift when dealing with a mask
* gfs2: Fix fallocate chunk size
* cdrom: do not call check_disk_change() inside cdrom_open()
* hwmon: (pmbus/adm1275) Accept negative page register values
* hwmon: (pmbus/max8688) Accept negative page register values
* perf/core: Fix perf_output_read_group()
* ASoC: topology: create TLV data for dapm widgets
* powerpc: Add missing prototype for arch_irq_work_raise()
* usb: gadget: ffs: Execute copy_to_user() with USER_DS set
* usb: gadget: ffs: Let setup() return USB_GADGET_DELAYED_STATUS
* usb: dwc2: Fix interval type issue
* ipmi_ssif: Fix kernel panic at msg_done_handler
* PCI: Restore config space on runtime resume despite being unbound
* MIPS: ath79: Fix AR724X_PLL_REG_PCIE_CONFIG offset
* xhci: zero usb device slot_id member when disabling and freeing a xhci 
slot
* KVM: lapic: stop advertising DIRECTED_EOI when in-kernel IOAPIC is in use
* i2c: mv64xxx: Apply errata delay only in standard mode
* ACPICA: acpi: acpica: fix acpi

[Kernel-packages] [Bug 1775235] Re: Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled

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

Bug description:
  == SRU Justification ==
  The bug reporter noticed that Xenial guests running on Nutanix AHV stopped
  booting after they were upgraded to 4.4.0-127. Only guests with scsi mq
  enabled suffered from this problem. AHV is one of the few hypervisor
  products to offer multiqueue for virtio-scsi devices.

  Upon further investigation, the saw that the kernel would hang during the
  scanning of scsi targets. More specifically, immediately after coming
  across a target without any luns present.

  It was found the following commit introduced this regression:
  commit f1f609d8015e1d34d39458924dcd9524fccd4307
  Author: Jay Vosburgh 
  Date: Thu Apr 19 21:40:00 2018 +0200

  The patch spins on the target's 'reqs' counter waiting for the target
  to quiesce.

  Further study revealed that virtio-scsi itself is broken in a way that it
  doesn't increment the 'reqs' counter when submitting requests on MQ in
  certain conditions. That caused the counter to go to -1 (on the completion
  of the first request) and the CPU to hang indefinitely.

  This regression is fixed by the requested SAUCE patch.

  
  == Fix ==
  UBUNTU: SAUCE: (no-up) virtio-scsi: Increment reqs counter.

  == Regression Potential ==
  Low.  Limited to virtio and fixes a regression.

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


  We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
  booting after they were upgraded to the latest kernel (4.4.0-127).
  Only guests with scsi mq enabled suffered from this problem. AHV is
  one of the few hypervisor products to offer multiqueue for virtio-scsi
  devices.

  Upon further investigation, we could see that the kernel would hang
  during the scanning of scsi targets. More specifically, immediately
  after coming across a target without any luns present. That's the
  first time the kernel destroys a target (given it doesn't have luns).
  This could be confirmed with gdb (attached to qemu's gdbserver):

  #0  0xc0045039 in ?? ()
  #1  0x88022c753c98 in ?? ()
  #2  0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
  at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322

  This shows the guest vCPU stuck on virtio-scsi's implementation of
  target_destroy. Despite lacking symbols, we managed to examine the
  virtio_scsi_target_state to see that the 'reqs' counter was invalid:

  (gdb) p *(struct virtio_scsi_target_state  *)starget->hostdata
  $6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq = 
0x88022cbdd9e8}
  (gdb)

  This drew our attention to the following patch which is exclusive to the 
Ubuntu kernel:
  commit f1f609d8015e1d34d39458924dcd9524fccd4307
  Author: Jay Vosburgh 
  Date:   Thu Apr 19 21:40:00 2018 +0200

  In a nutshell, the patch spins on the target's 'reqs' counter waiting for the 
target to quiesce:
  --- a/drivers/scsi/virtio_scsi.c
  +++ b/drivers/scsi/virtio_scsi.c
  @@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target 
*starget)
   static void virtscsi_target_destroy(struct scsi_target *starget)
   {
  struct virtio_scsi_target_state *tgt = starget->hostdata;
  +
  +   /* we can race with concurrent virtscsi_complete_cmd */
  +   while (atomic_read(>reqs))
  +   cpu_relax();
  kfree(tgt);
   }

  Personally, I think this is a catastrophic way of waiting for a target
  to quiesce since virtscsi_target_destroy() is called with IRQs
  disabled from scsi_scan.c:scsi_target_destroy(). Devices which take a
  long time to quiesce during a target_destroy() could hog the CPU for
  relatively long periods of time.

  Nevertheless, further study revealed that virtio-scsi itself is broken
  in a way that it doesn't increment the 'reqs' counter when submitting
  requests on MQ in certain conditions. That caused the counter to go to
  -1 (on the completion of the first request) and the CPU to hang
  indefinitely.

  The following patch fixes the issue:

  --- old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04 
10:23:07.0 -0700
  +++ new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05 
10:03:29.083428545 -0700
  @@ -641,9 +641,10 @@
  scsi_target(sc->device)->hostdata;
  struct virtio_scsi_vq *req_vq;

  -   if (shost_use_blk_mq(sh))
  +   if (shost_use_blk_mq(sh)) {
  req_vq = virtscsi_pick_vq_mq(vscsi, sc);
  -   else

[Kernel-packages] [Bug 1511002] Re: Computer freezes/crashes while using GNOME

** Changed in: linux
   Status: Unknown => 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/1511002

Title:
  Computer freezes/crashes while using GNOME

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

Bug description:
  I think I have two issues (may related) with the Intel driver for my
  graphic card. Sometimes the text is shown as garbage, and every other
  day (after suspending) it crashes.  As I have not figure out what is
  the SysRq magic key is in this new laptop (Lenovo x250), I can only
  recover control on my computer after pressing the power off button.

  I cannot go to a vt. No nothing.  I hope the follow call trace is
  related to that, although it should not be there in any case :-)

  
  Oct 27 14:49:33 sai kernel: [38682.963345] [ cut here 
]
  Oct 27 14:49:33 sai kernel: [38682.963368] WARNING: CPU: 0 PID: 0 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:11100 
intel_check_page_flip+0xfc/0x110 [i915]()
  Oct 27 14:49:33 sai kernel: [38682.963369] Kicking stuck page flip: queued at 
2122948, now 2122952
  Oct 27 14:49:33 sai kernel: [38682.963370] Modules linked in: ses enclosure 
uas usb_storage hid_generic usbhid hid msr rfcomm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm binfmt_misc 
bnep arc4 int
  el_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core crct10dif_pclmul 
v4l2_common videodev crc32_pclmul iwlmvm snd_hda_codec_hdmi 
snd_hda_codec_realtek bt
  usb media snd_hda_codec_generic ghash_clmulni_intel btrtl mac80211 btbcm 
btintel bluetooth aesni_intel snd_hda_intel aes_x86_64 snd_hda_codec lrw 
gf128mul snd_hda_core glue_helper snd_hwdep ablk_helper thinkpad_acpi cryptd 
iwlwifi snd_pcm
   nvram snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds cfg80211 joydev 
snd_seq serio_raw rtsx_pci_ms snd_seq_device memstick snd_timer snd mei_me 
soundcore shpchp mei lpc_ich mac_hid parport_pc ppdev sunrpc lp parport autofs4 
rtsx_
  pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper ahci libahci drm 
ptp rtsx_pci pps_core wmi video
  Oct 27 14:49:33 sai kernel: [38682.963414] CPU: 0 PID: 0 Comm: swapper/0 
Tainted: GW  OE   4.2.0-16-generic #19-Ubuntu
  Oct 27 14:49:33 sai kernel: [38682.963415] Hardware name: LENOVO 
20CMCTO1WW/20CMCTO1WW, BIOS N10ET36W (1.15 ) 06/19/2015
  Oct 27 14:49:33 sai kernel: [38682.963416]   4c472c3169d69ebc 
88022dc03d48 817e8c09
  Oct 27 14:49:33 sai kernel: [38682.963418]   88022dc03da0 
88022dc03d88 8107b3c6
  Oct 27 14:49:33 sai kernel: [38682.963420]  88022dc03db8 8800b872d000 
8802201e2000 8800b872d1a8
  Oct 27 14:49:33 sai kernel: [38682.963421] Call Trace:
  Oct 27 14:49:33 sai kernel: [38682.963422][] 
dump_stack+0x45/0x57
  Oct 27 14:49:33 sai kernel: [38682.963429]  [] 
warn_slowpath_common+0x86/0xc0
  Oct 27 14:49:33 sai kernel: [38682.963431]  [] 
warn_slowpath_fmt+0x55/0x70
  Oct 27 14:49:33 sai kernel: [38682.963443]  [] 
intel_check_page_flip+0xfc/0x110 [i915]
  Oct 27 14:49:33 sai kernel: [38682.963453]  [] 
gen8_irq_handler+0x325/0x590 [i915]
  Oct 27 14:49:33 sai kernel: [38682.963456]  [] 
handle_irq_event_percpu+0x74/0x180
  Oct 27 14:49:33 sai kernel: [38682.963457]  [] 
handle_irq_event+0x49/0x70
  Oct 27 14:49:33 sai kernel: [38682.963459]  [] 
handle_edge_irq+0x81/0x150
  Oct 27 14:49:33 sai kernel: [38682.963461]  [] 
handle_irq+0x25/0x40
  Oct 27 14:49:33 sai kernel: [38682.963463]  [] 
do_IRQ+0x4f/0xe0
  Oct 27 14:49:33 sai kernel: [38682.963465]  [] 
common_interrupt+0x6b/0x6b
  Oct 27 14:49:33 sai kernel: [38682.963465][] ? 
enqueue_hrtimer+0x44/0x80
  Oct 27 14:49:33 sai kernel: [38682.963469]  [] ? 
cpuidle_enter_state+0x130/0x270
  Oct 27 14:49:33 sai kernel: [38682.963471]  [] ? 
cpuidle_enter_state+0x10b/0x270
  Oct 27 14:49:33 sai kernel: [38682.963472]  [] 
cpuidle_enter+0x17/0x20
  Oct 27 14:49:33 sai kernel: [38682.963474]  [] 
call_cpuidle+0x32/0x60
  Oct 27 14:49:33 sai kernel: [38682.963475]  [] ? 
cpuidle_select+0x13/0x20
  Oct 27 14:49:33 sai kernel: [38682.963476]  [] 
cpu_startup_entry+0x268/0x320
  Oct 27 14:49:33 sai kernel: [38682.963479]  [] 
rest_init+0x7c/0x80
  Oct 27 14:49:33 sai kernel: [38682.963481]  [] 
start_kernel+0x48b/0x4ac
  Oct 27 14:49:33 sai kernel: [38682.963483]  [] ? 
early_idt_handler_array+0x120/0x120
  Oct 27 14:49:33 sai kernel: [38682.963484]  [] 
x86_64_start_reservations+0x2a/0x2c
  Oct 27 14:49:33 sai kernel: [38682.963486]  [] 
x86_64_start_kernel+0x14a/0x16d
  Oct 27 14:49:33 sai kernel: [38682.963487] ---[ end trace 2d9bf7218712045a 
]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19

[Kernel-packages] [Bug 1775483] Re: Bionic update: upstream stable patchset 2018-06-06

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

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

Title:
  Bionic update: upstream stable patchset 2018-06-06

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2018-06-06 (ported from v4.14.38 and v4.16.6)
     from git://git.kernel.org/

  kprobes: Fix random address output of blacklist file
  s390/cpum_cf: rename IBM z13/z14 counter names
  hwmon: (k10temp) Add support for AMD Ryzen w/ Vega graphics
  hwmon: (k10temp) Add temperature offset for Ryzen 2700X
  VSOCK: make af_vsock.ko removable again
  virtio-net: add missing virtqueue kick when flushing packets
  bnxt_en: Fix memory fault in bnxt_ethtool_init()
  s390/qeth: handle failure on workqueue creation
  s390/qeth: avoid control IO completion stalls
  s390/qeth: fix error handling in adapter command callbacks
  l2tp: fix {pppol2tp, l2tp_dfs}_seq_stop() in case of seq_file overflow
  l2tp: hold reference on tunnels printed in l2tp/tunnels debugfs file
  l2tp: hold reference on tunnels printed in pppol2tp proc file
  l2tp: hold reference on tunnels in netlink dumps
  vmxnet3: fix incorrect dereference when rxvlan is disabled
  net: stmmac: Disable ACS Feature for GMAC >= 4
  net: mvpp2: Fix DMA address mask size
  docs: ip-sysctl.txt: fix name of some ipv6 variables
  ACPI / video: Only default only_lcd to true on Win8-ready _desktops_
  s390/uprobes: implement arch_uretprobe_is_alive()
  s390/dasd: fix IO error for newly defined devices
  s390/cio: update chpid descriptor after resource accessibility event
  tracing: Fix missing tab for hwlat_detector print format
  block/swim: Fix IO error at end of medium
  block/swim: Fix array bounds check
  block/swim: Select appropriate drive on device open
  block/swim: Rename macros to avoid inconsistent inverted logic
  block/swim: Remove extra put_disk() call from error path
  block/swim: Don't log an error message for an invalid ioctl
  block/swim: Check drive type
  m68k/mac: Don't remap SWIM MMIO region
  cdrom: information leak in cdrom_ioctl_media_changed()
  scsi: mptsas: Disable WRITE SAME
  commoncap: Handle memory allocation failure.
  microblaze: Setup dependencies for ASM optimized lib functions
  s390: correct module section names for expoline code revert
  KVM: s390: force bp isolation for VSIE
  virtio_net: fix adding vids on big-endian
  virtio_net: split out ctrl buffer
  net: ethernet: ti: cpsw: fix tx vlan priority mapping
  llc: fix NULL pointer deref for SOCK_ZAPPED
  llc: hold llc_sap before release_sock()
  net: sched: ife: check on metadata length
  net: sched: ife: handle malformed tlv length
  tcp: clear tp->packets_out when purging write queue
  net: sched: ife: signal not finding metaid
  strparser: Fix incorrect strp->need_bytes value.
  amd-xgbe: Only use the SFP supported transceiver signals
  strparser: Do not call mod_delayed_work with a timeout of LONG_MAX
  amd-xgbe: Improve KR auto-negotiation and training
  sctp: do not check port in sctp_inet6_cmp_addr
  amd-xgbe: Add pre/post auto-negotiation phy hooks
  vlan: Fix reading memory beyond skb->tail in skb_vlan_tagged_multi
  pppoe: check sockaddr length in pppoe_connect()
  tipc: add policy for TIPC_NLA_NET_ADDR
  packet: fix bitfield update race
  team: fix netconsole setup over team
  net/smc: fix shutdown in state SMC_LISTEN
  team: avoid adding twice the same option to the event list
  net: fix deadlock while clearing neighbor proxy table
  tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
  net: af_packet: fix race in PACKET_{R|T}X_RING
  tcp: don't read out-of-bounds opsize
  llc: delete timers synchronously in llc_sk_free()
  net: validate attribute sizes in neigh_dump_table()
  l2tp: check sockaddr length in pppol2tp_connect()
  KEYS: DNS: limit the length of option strings
  ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts
  ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
  bonding: do not set slave_dev npinfo before slave_enable_netpoll in 
bond_enslave
  Revert "ath10k: send (re)assoc peer command when NSS changed"
  tpm: add retry logic
  tpm: tpm-interface: fix tpm_transmit/_cmd kdoc
  tpm: cmd_ready command can be issued only after granting locality
  i40e: Fix attach VF to VM issue
  drm: bridge: dw-hdmi:

[Kernel-packages] [Bug 1775856] Re: register on binfmt_misc may overflow and crash the system

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

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

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

Title:
  register on binfmt_misc may overflow and crash the system

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

Bug description:
  [Impact]
  When registering a new binfmt_misc handler, it is possible to overflow
  the offset to get a negative value, which might crash the system, or
  possibly leak kernel data.

  Here is a crash log when 25 was used as an offset:

BUG: unable to handle kernel paging request at 989cfd6edca0
IP: load_misc_binary+0x22b/0x470 [binfmt_misc]
PGD 1ef3e067 P4D 1ef3e067 PUD 0
Oops:  [#1] SMP NOPTI
Modules linked in: binfmt_misc kvm_intel ppdev kvm irqbypass joydev 
input_leds serio_raw mac_hid parport_pc qemu_fw_cfg parpy
CPU: 0 PID: 2499 Comm: bash Not tainted 4.15.0-22-generic #24-Ubuntu
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1 
04/01/2014
RIP: 0010:load_misc_binary+0x22b/0x470 [binfmt_misc]
Call Trace:
  search_binary_handler+0x97/0x1d0
  do_execveat_common.isra.34+0x667/0x810
  SyS_execve+0x31/0x40
  do_syscall_64+0x73/0x130
  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  Use kstrtoint instead of simple_strtoul.  It will work as the code
  already set the delimiter byte to '\0' and we only do it when the field
  is not empty.

  [Test Case]
  Tested with offsets -1, 25, UINT_MAX and INT_MAX.  Also tested
  with examples documented at Documentation/admin-guide/binfmt-misc.rst
  and other registrations from packages on Ubuntu.

  [Regression]
  Fail to register valid types. This was tested with a bionic kernel with the 
patch.

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

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

[Kernel-packages] [Bug 1744173] Re: rfi-flush: Switch to new linear fallback flush

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

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

Title:
  rfi-flush: Switch to new linear fallback flush

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

Bug description:
  [Impact]
  Change flush method from "congruence-first with dependencies" to "linear with 
no dependencies", which increases flush performance by 8x on P8, and
  3x on P9. Measured with null syscall loop, which will have the flush area in 
the L2 cache.

  The flush also becomes simpler and more adaptable to different cache
  geometries.

  [Test Case]
  TBD.

  [Regression Potential]
  The risk is deemed low since the changes are confined to POWER only and the 
provided test kernels have been tested by IBM.

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

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

[Kernel-packages] [Bug 1721987] Re: No sound from right audio channel

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=197801.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-11-07T16:58:32+00:00 jcs wrote:

Created attachment 260537
dmesg

No audio comes out of the right speaker on the laptop. When playing a
test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the
right-channel audio is never heard (i.e., it does not get converted into
mono and played through the left speaker).

When plugging in headphones, audio is heard from both channels.

In Windows, both speakers work, so it is not a physical problem with the
speakers.

This is being moved upstream from the Ubuntu bug at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987

alsa-info.sh output at http://www.alsa-
project.org/db/?f=dbe13f8a856c2178d5794cb787b153b6ce311a80

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987/comments/9


On 2017-11-07T17:02:25+00:00 jcs wrote:

Created attachment 260539
alsa-info.sh output

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987/comments/11


On 2018-02-25T22:37:19+00:00 jerin04 wrote:

Hello, is this bug assigned to anyone? Never used bug tracker before.

Just want put more voice to this bug as I have a Matebook X as well.
Only one of the speakers work. I am sure there are others buying this
machine and wants to run linux variants.

Some more info in case it helps: https://github.com/lidel/linux-on-
huawei-matebook-x-2017

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987/comments/12


On 2018-03-12T05:31:32+00:00 samsau wrote:

Bump. 
I am one of the aforementioned 'others'. The problem is rather annoying and 
hasn't been solved as of 4.15.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987/comments/13


On 2018-06-05T06:26:52+00:00 hajek1 wrote:

Mee too. I can confirm the problem on 4.16.13-1-ARCH kernel.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987/comments/15


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  No sound from right audio channel

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

Bug description:
  No audio comes out of the right speaker on the laptop.  When playing a
  test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the
  right-channel audio is never heard (i.e., it does not get converted
  into mono and played through the left speaker).

  When plugging in headphones, audio is heard from both channels.

  In Windows, both speakers work, so it is not a physical problem with
  the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1127 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 12:58:01 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: HUAWEI HUAWEI MateBook X
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2017
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: HUAWEI MateBook X
  dmi.board.vendor: HUAWEI
  dmi.board.version: 2.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr:
  dmi.product.family: HUAWEI MateBook
  dmi.product.name:

[Kernel-packages] [Bug 1664072] Re: TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised.

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=194569.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-02-12T22:39:08+00:00 caravena wrote:

Open bug in launchpad.net
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664072

"dmesg:
[ 7578.057461] TCP: wlp1s0: Driver has suspect GRO implementation, TCP 
performance may be compromised."

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664072/comments/2


On 2018-06-05T12:03:22+00:00 pedretti.fabio wrote:

This harmless warning should be fixed backporting [0] to 4.9 series.

[0]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0b9aefea860063bb39e36bd7fe6c7087fed0ba87

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664072/comments/5


On 2018-06-08T15:15:25+00:00 marcelo.leitner wrote:

I went over iwlwifi commits since then and I couldn't find any issue
regarding TCP/GSO. That said, I agree that it seems to be harmless in
that setup and that backporting 0b9aefea860063bb39e36bd7fe6c7087fed0ba87
should help on identifying if it's a false-positive or not.

Someone needs to send an email to netdev@ asking for it, though. kernel
bugzilla is not how it's done for networking subsystem. More info in
./Documentation/networking/netdev-FAQ.txt . Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664072/comments/6


On 2018-06-08T15:40:05+00:00 pedretti.fabio wrote:

BTW, I had this same warning with vmxnet3 driver with 4.9. I tried a
newer kernel and the message didn't appear. I posted my findings here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864642#95 - for
reference:

===
It looks like the warning appeared with this first commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dcb17d22e1c2cd72e72190c736349a675362b3bc
but was later corrected with this second one:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0b9aefea860063bb39e36bd7fe6c7087fed0ba87

The first commit was merged in the 4.9 tree, but not the second one (at
least not up to 4.9.106), and was only merged in 4.11.

So I would conclude the warning may be harmless, unless you got it on a
>= 4.11 kernel. And I also verified I don't get it on such a newer
kernel.

I would close this bug, but it may eventually be nice to backport the second 
commit in 4.9 to avoid the harmless warning.
===

Searching on the net, there are other reports with the same issue and
with various other drivers.

I added in CC: here the net/ipv4 maintainers I found in MAINTAINERS
file:

NETWORKING [IPv4/IPv6]
M:  "David S. Miller" 
M:  Alexey Kuznetsov 
M:  Hideaki YOSHIFUJI 
L:  net...@vger.kernel.org
T:  git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
S:  Maintained
F:  net/ipv4/
F:  net/ipv6/
F:  include/net/ip*
F:  arch/x86/net/*

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664072/comments/7


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

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

Title:
  TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance
  may be compromised.

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux package in Debian:
  Confirmed

Bug description:
  dmesg:
  [ 7578.057461] TCP: wlp1s0: Driver has suspect GRO implementation, TCP 
performance may be compromised.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-15-generic 4.9.0-15.16
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2378 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2378 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Feb 12 19:34:40 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (567 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-15-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro

[Kernel-packages] [Bug 1745636] Re: RT3290 Wireless 802.11n 1T/1R PCIe don't work.