Re: [Kernel-packages] [Bug 1823780] Re: Touchpad stopped working suddenly

2019-04-08 Thread nonidh singh
I resolved it some how by going to recovery mode. The problem was that the
touchpad was not even showing in the xinput and also in proc. So I think
the kernel version may be responsible.

On Tue, 9 Apr 2019, 10:50 Kai-Heng Feng, 
wrote:

> Does it happen to previous kernel release, 4.15.0-46?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1823780
>
> Title:
>   Touchpad stopped working suddenly
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have dual boot with windows from year.The touchpad has been working
>   fine till now but it stopped working suddenly.It still works on
>   windows though.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-47-generic 4.15.0-47.50
>   ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
>   Uname: Linux 4.15.0-47-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  nsk06  2240 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Apr  9 05:36:08 2019
>   HibernationDevice: RESUME=UUID=c854a58f-a6c2-4f17-bb97-7a7456960278
>   InstallationDate: Installed on 2018-03-19 (385 days ago)
>   InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
> (20170215.2)
>   MachineType: HP HP ENVY x360 Convertible 15m-bp1xx
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic
> root=UUID=81ecfc7a-2ce4-48da-a626-08c07c96a86d ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-47-generic N/A
>linux-backports-modules-4.15.0-47-generic  N/A
>linux-firmware 1.173.3
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to bionic on 2018-08-06 (245 days ago)
>   dmi.bios.date: 07/24/2017
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.22
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 83C8
>   dmi.board.vendor: HP
>   dmi.board.version: 32.60
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPENVYx360Convertible15m-bp1xx:pvrType1ProductConfigId:rvnHP:rn83C8:rvr32.60:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV HP Envy
>   dmi.product.name: HP ENVY x360 Convertible 15m-bp1xx
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823780/+subscriptions
>

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

Title:
  Touchpad stopped working suddenly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have dual boot with windows from year.The touchpad has been working
  fine till now but it stopped working suddenly.It still works on
  windows though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nsk06  2240 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 05:36:08 2019
  HibernationDevice: RESUME=UUID=c854a58f-a6c2-4f17-bb97-7a7456960278
  InstallationDate: Installed on 2018-03-19 (385 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP ENVY x360 Convertible 15m-bp1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=81ecfc7a-2ce4-48da-a626-08c07c96a86d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-06 (245 days ago)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83C8
  dmi.board.vendor: HP
  dmi.board.version: 32.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPENVYx360Convertible15m-bp1xx:pvrType1ProductConfigId:rvnHP:rn83C8:rvr32.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bp1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-04-08 Thread Juerg Haefliger
Stefan NACK'ed the series. For some unknown reason that email did make
it into the archive so here is ist content:

> Since commit fb1522e099f0 ("KVM: update to new mmu_notifier semantic
> v2", 2017-08-31), the MMU notifier code in KVM no longer calls the
> kvm_unmap_hva callback.  This removes the PPC implementations of
> kvm_unmap_hva().  

This is not really the way SRUs should be done. We cannot remove support for
interfaces after release. Also the amount of change as a requisite should be
kept as minimal as possible. This just feels like too many changes without a
strong argument on why this must be done that way.

-Stefan

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-04-08 Thread Kai-Heng Feng
What's the output of `dpkg -l | grep linux-image` and `apt show linux-
image-generic`?

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

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

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.

  [Fix]
  The commit that causes the regression works in mainline, so there are
  some functional dependencies are not in 4.15.

  Finding those dependencies can be hard since I don't have the hardware
  to test with, also pulling new commits may cause new regression. So the
  safest way to deal with this bug is to simply revert the regression
  commit.

  [Test]
  User confirmed reverting the commit can fix the issue.

  [Regression Potential]
  Low. Realtek 8723be works without this commit.

  === Original Bug Report ===
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 
4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted

2019-04-08 Thread Kai-Heng Feng
Download those files into a new directory, cd to the directory and run
`sudo dpkg -i *deb`.

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

Title:
  [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric
  background noise when volume is not muted

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start 
hearing a static/electric (some internal?) sound if the volume isn't muted. 
Something similar occurs with my other earbuds with mic, just much quieter and 
less noticable. It works fine on Windows 10 running on the same machine, and on 
my Android phone. I don't notice is when something is playing, but the 
frequency of the sound changes when I play something, then pause it, the 
background noise will sound slightly different.
  This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB 
and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with 
alsamixer and pavucontrol settings, and nothing fixed this background noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidkoplik   1891 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 20:17:59 2018
  InstallationDate: Installed on 2018-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2019-04-08 Thread Kai-Heng Feng
Please attach dmesg after the hotkey gets pressed.

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+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 1819786] Re: 4.15 kernel ip_vs --ops causes performance and hang problem

2019-04-08 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ From the commit message:
+ "Connections in One-packet scheduling mode (-o, --ops) are
+ removed with refcnt=0 because they are not hashed in conn table."
+ 
+ [Fix]
+ From the commit message:
+ "To avoid refcount_dec reporting this as error, change them to be
+ removed with refcount_dec_if_one as all other connections."
+ 
+ [Test]
+ The bug reporter has a reproducer and confirmed this commit fixes the
+ issue.
+ 
+ [Regression Potential]
+ Low. Fix for a specific use case, and it's in upstream for a while.
+ 
+ === Original Bug Report ===
  On our 16.04LTS (and earlier) systems we used the ipvsadm --ops UDP
  support (one-packet scheduling) to get a better distribution amongst
  our real servers behind the load-balancer for some small subset of
  applications.
  
  This has worked fine through the 4.4.0-xxx kernels. But when we started
  a program to upgrade systems to use the 4.15 series of kernels to take
  advantage of new facilities, the subset of systems which used the --ops
  option ran into problems. Everything else with the 4.15 kernels appeared
  to work well.
  
  This issue was reported in #1817247 against 16.04LTS with the HWE 4.15 kernel
  but has not received any acknowledgement after having been reported weeks
  ago.   So we have moved on to confirm that a stock 18.04LTS system with the
  latest expected/standard 4.15 kernel also has this issue as well and report
  that here.  Perhaps this will get more attention.
  
  The issue appears to have been the change in the ip_vs module from using
  "atomic_*()" increment/decrement functions in the 4.4 kernel to instead
  use "refcount_*()" functions in a later kernel, including the 4.15 one
  we switched to. Unfortunately, the simple refcount_dec() function was
  inadequate, in putting out a time-consuming message and handling when
  the refcount dropped to zero, which is expected in the case of --ops
  support that retains no state post packet delivery. I will upload an
  attachment with the sample messages that get put out at packet arrival
  rate, which destroys performance of course. This test VM reports the
  identical errors we see in our production servers, but at least throwing
  only a couple of test --ops packets at it doesn't crash/hang the 18.04 system
  as it did in the 16.04 VM reported earlier.   And in production, with the
  far greater packet rates, our systems fail since the attached call backtrace
  *** appears on every packet!! ***
  
  This issue was apparently already recognized as an error and has appeared
  as a fix in upstream kernels. This is a reference to the 4.17 version
  of the fix that we'd like to see incorporated into the next possible
  kernel maintenance release:
  
  
https://github.com/torvalds/linux/commit/a050d345cef0dc6249263540da1e902bba617e43
  #diff-75923493f6e3f314b196a8223b0d6342
  
  We have successfully used the livepatch facility to build a livepatch .ko
  with the above diffs on our 4.15.0-36 system and successfully demonstrated
  the contrast in good/bad behavior with/without the livepatch module
  loaded. But we'd rather not have to build a version of livepatch.ko for
  each kernel maintenance release, such as the 4.5.0-46 kernel here used to
  demonstrate the issue persists in the Ubuntu mainline distro.
  
  The problem is easy to generate, with only a couple of packets
  and a simple configuration. Here's a very basic test (addresses
  rewritten/obscured) version of an example configuration for 2 servers
  that worked on my test VM:
  
  ipvsadm -A -f 100 -s rr --ops
  ipvsadm -a -f 100 -r 10.129.131.227:0 -g -w 
  ipvsadm -a -f 100 -r 10.129.131.228:0 -g -w 
  iptables -t mangle -A PREROUTING -d 172.16.5.1/32 -j MARK --set-xmark 
0x64/0x
  ifconfig lo:0 172.16.5.1/32 up
  
  Routing and addressing to achieve the above, or adaptation for one's
  own test environment, is left to the tester.  I just added alias 10.129.131.x
  addresses on my "outbound" interface and a static route for 172.16.5.1 to my
  client system so the test packets arrived on the "inbound" interface.
  
  I set up routing and addresses on my 2 NIC test such that packets arrived
  on my test machine's eth1 NIC and were directed by ip_vs out the eth2. To
  test, all I did was throw a few UDP packets via traceroute at the address
  on the iptables/firewall mark rule so that the eth1 interface of the
  test system was the traceroute system's default gateway:
  
-   traceroute -m 2 172.16.5.1
+   traceroute -m 2 172.16.5.1
  
  Without the fix my test ip_vs system either hangs or puts out messages
  as per the attached. With our livepatch module using the above commit's
  contents, all is well. Both of the test ("real" as opposed to "virtual")
  servers configured above via ipvsadm, get packets and no errors are
  reported in the logs.
  
- Let me know of anything 

Re: [Kernel-packages] [Bug 1822085] Re: Often the VGA screen stops working after screen saver was on

2019-04-08 Thread Sebastian Andersson
Yes, that solved it! Thanks!

On Thu, Mar 28, 2019 at 7:15 PM Timo Aaltonen 
wrote:

> try linux-oem -1035 from bionic-proposed, it has ~50 commits backported
> from 5.0 to i915 driver which should help with these issues
>
> ** Description changed:
>
>   I have two connected external monitors. They are connected through a
>   Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
>   the VGA monitor complains about the resolution and will not work after
>   the screen saver has been active (and putting the monitors to sleep).
>   When shutting down the system, it then hangs and I have to force a
>   shutdown with the power button.
>
>   There seems to be a kernel crash before as seen in the dmesg log.
> +
> +
> + ProblemType: Bug
> + DistroRelease: Ubuntu 18.04
> + Package: xorg 1:7.7+19ubuntu7.1
> + ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18
> + Uname: Linux 4.15.0-1034-oem x86_64
> + ApportVersion: 2.20.9-0ubuntu7.6
> + Architecture: amd64
> + BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
> + CompositorRunning: None
> + CurrentDesktop: ubuntu:GNOME
> + Date: Thu Mar 28 12:04:07 2019
> + DistUpgraded: Fresh install
> + DistributionChannelDescriptor:
> +  # This is the distribution channel descriptor for the OEM CDs
> +  # For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
> +  canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
> + DistroCodename: bionic
> + DistroVariant: ubuntu
> + DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed
> + ExtraDebuggingInterest: Yes
> + GraphicsCard:
> +  Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
> +Subsystem: Dell Device [1028:08af]
> + InstallationDate: Installed on 2019-02-12 (44 days ago)
> + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
> 20180608-09:38
> + MachineType: Dell Inc. XPS 13 9380
> + ProcEnviron:
> +  LANG=sv_SE.UTF-8
> +  SHELL=/bin/bash
> +  TERM=xterm-256color
> +  XDG_RUNTIME_DIR=
> +  PATH=(custom, no user)
> + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1034-oem
> root=UUID=0b807479-b451-4f56-b9cc-307300b68200 ro quiet splash vt.handoff=1
> + SourcePackage: xorg
> + Symptom: display
> + UpgradeStatus: No upgrade log present (probably fresh install)
> + dmi.bios.date: 02/14/2019
> + dmi.bios.vendor: Dell Inc.
> + dmi.bios.version: 1.2.1
> + dmi.board.name: 0KTDY6
> + dmi.board.vendor: Dell Inc.
> + dmi.board.version: A00
> + dmi.chassis.type: 10
> + dmi.chassis.vendor: Dell Inc.
> + dmi.modalias:
> dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTDY6:rvrA00:cvnDellInc.:ct10:cvr:
> + dmi.product.family: XPS
> + dmi.product.name: XPS 13 9380
> + dmi.sys.vendor: Dell Inc.
> + version.compiz: compiz N/A
> + version.libdrm2: libdrm2 2.4.95-1~18.04.1
> + version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
> + version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
> + version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
> + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
> + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
> + version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1
> + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
>
> ** Package changed: xorg (Ubuntu) => linux-oem (Ubuntu)
>
> ** Changed in: linux-oem (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1822085
>
> Title:
>   Often the VGA screen stops working after screen saver was on
>
> Status in linux-oem package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have two connected external monitors. They are connected through a
>   Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
>   the VGA monitor complains about the resolution and will not work after
>   the screen saver has been active (and putting the monitors to sleep).
>   When shutting down the system, it then hangs and I have to force a
>   shutdown with the power button.
>
>   There seems to be a kernel crash before as seen in the dmesg log.
>
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18
>   Uname: Linux 4.15.0-1034-oem x86_64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Mar 28 12:04:07 2019
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
># This is the distribution channel descriptor for the OEM CDs
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
>   DistroCodename: bionic
>   

[Kernel-packages] [Bug 1332824] Re: [Samsung XE700T1C-A01FR] Smartpad not properly recognised

2019-04-08 Thread Kai-Heng Feng
Please attach dmesg.

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

Title:
  [Samsung XE700T1C-A01FR] Smartpad not properly recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expecting at least the smartpad to be properly recognised with the
  bare minimum multi-touch gesture: two-fingers right click, side
  scrolling, two-fingers scrolling, mouse speed.

  xinput -list gives:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Wacom ISDv4 EC Pen stylus   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Atmel Atmel maXTouch Digitizer  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ USB Keyboard+SmartPad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ Wacom ISDv4 EC Pen eraser   id=16   [slave  pointer 
 (2)]
  ⎜   ↳ Asus gaming Mouse (G112)id=19   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ WebCam SC-50AFL11C54N   id=11   [slave  
keyboard (3)]
  ↳ USB Keyboard+SmartPad   id=12   [slave  
keyboard (3)]
  ↳ WebCam SC-20HDM12347N   id=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=15   [slave  
keyboard (3)]
  ↳ Chicony USB Keyboardid=17   [slave  
keyboard (3)]
  ↳ Chicony USB Keyboardid=18   [slave  
keyboard (3)]
  ↳ Acer Crystal Eye Webcam id=20   [slave  
keyboard (3)]

  Note that "USB Keyboard+SmartPad" is present twice (id 12 and 13)

  Also note that running
   xinput test 13
  doesn't detect any multitouch on the smartpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 21 15:52:14 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
  InstallationDate: Installed on 2014-06-18 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=1fdb1c66-705c-4c1a-8d6c-d363ad0e53b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-A01FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

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

2019-04-08 Thread Kai-Heng Feng
Gordon,
Please file a separate bug report, thanks.

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

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

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

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 1823780] Re: Touchpad stopped working suddenly

2019-04-08 Thread Kai-Heng Feng
Does it happen to previous kernel release, 4.15.0-46?

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

Title:
  Touchpad stopped working suddenly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have dual boot with windows from year.The touchpad has been working
  fine till now but it stopped working suddenly.It still works on
  windows though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nsk06  2240 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 05:36:08 2019
  HibernationDevice: RESUME=UUID=c854a58f-a6c2-4f17-bb97-7a7456960278
  InstallationDate: Installed on 2018-03-19 (385 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP ENVY x360 Convertible 15m-bp1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=81ecfc7a-2ce4-48da-a626-08c07c96a86d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-06 (245 days ago)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83C8
  dmi.board.vendor: HP
  dmi.board.version: 32.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPENVYx360Convertible15m-bp1xx:pvrType1ProductConfigId:rvnHP:rn83C8:rvr32.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bp1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823780/+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 1821383] Re: synaptics touchpoint fails after resume

2019-04-08 Thread Kai-Heng Feng
Please comment out "blacklist i2c_i801" in
/etc/modprobe.d/blacklist.conf, reboot and test again.

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

Title:
  synaptics touchpoint fails after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To workaround bug #924648 I've installed the following:

  $ cat /etc/udev/rules.d/10-trackpoint.rules 
  ACTION=="add|change",
  SUBSYSTEM=="input",
  ATTR{name}=="TPPS/2 IBM TrackPoint",
  ATTR{device/sensitivity}="250",
  ATTR{device/speed}="250",

  While this works I now sometimes get a broken pointer after suspend.
  dmesg shows this at resume:

  [353671.884852] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [353672.381746] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [353672.845761] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  After some time it resets and the pointer is back. Most of the time
  just this is shown:

  [353852.538962] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [353852.735990] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input52

  But I did get a timeout call trace once:

  [ 5676.512616] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0
  [ 5677.453153] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [ 5677.643970] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input21
  [ 5800.035392] INFO: task kworker/0:2:9739 blocked for more than 120 seconds.
  [ 5800.035402]   Tainted: G   OE4.15.0-45-generic #48-Ubuntu
  [ 5800.035406] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5800.035410] kworker/0:2 D0  9739  2 0x8000
  [ 5800.035424] Workqueue: events_long serio_handle_event
  [ 5800.035427] Call Trace:
  [ 5800.035439]  __schedule+0x291/0x8a0
  [ 5800.035445]  ? schedule_timeout+0x165/0x350
  [ 5800.035453]  schedule+0x2c/0x80
  [ 5800.035460]  __kernfs_remove.part.12+0x175/0x1f0
  [ 5800.035467]  ? wait_woken+0x80/0x80
  [ 5800.035474]  kernfs_remove_by_name_ns+0x54/0xa0
  [ 5800.035479]  remove_files.isra.1+0x35/0x70
  [ 5800.035484]  sysfs_remove_group+0x44/0x90
  [ 5800.035488]  sysfs_remove_groups+0x2e/0x50
  [ 5800.035493]  device_remove_groups+0x12/0x20
  [ 5800.035508]  trackpoint_disconnect+0x44/0x70 [psmouse]
  [ 5800.035517]  psmouse_disconnect+0xfe/0x190 [psmouse]
  [ 5800.035525]  serio_disconnect_driver+0x36/0x50
  [ 5800.035531]  serio_driver_remove+0x15/0x20
  [ 5800.035539]  device_release_driver_internal+0x15b/0x240
  [ 5800.035544]  device_release_driver+0x12/0x20
  [ 5800.035548]  serio_disconnect_port+0x98/0xb0
  [ 5800.035553]  serio_handle_event+0x18e/0x250
  [ 5800.035559]  process_one_work+0x1de/0x410
  [ 5800.035565]  worker_thread+0x32/0x410
  [ 5800.035572]  kthread+0x121/0x140
  [ 5800.035576]  ? process_one_work+0x410/0x410
  [ 5800.035582]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 5800.035589]  ? do_syscall_64+0x73/0x130
  [ 5800.035594]  ? SyS_exit+0x17/0x20
  [ 5800.035600]  ret_from_fork+0x35/0x40
  [ 5858.636930] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [ 5858.872453] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input22

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   26606 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:20:56 2019
  InstallationDate: Installed on 2018-05-31 (295 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 5986:0706 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FAS5TS00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=0206141b-5758-4895-bbbd-8022b1e78519 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  

[Kernel-packages] [Bug 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

2019-04-08 Thread bugproxy
** Tags removed: verification-needed-bionic
** Tags added: 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/1719545

Title:
  [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop
  Idle_Stats

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 15396
  Duration: 6625668881

  
  cpu monitor will print the results of all the 3 available idle_stats .

  The first stop -> stop0_lite stats
  and
  The second stop -> stop1_lite stats.

  cpupower monitor header prints the header list by getting the name of
  the idle stats.

  name  (name description)
  snoo   [T] -> snooze
  stop   [T] -> stop0_lite
  stop   [T] -> stop1_lite

  We can change the header to be 

[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze

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

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

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

Title:
  Docking thinkpad laptop causes a complete system freeze

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since upgrading to Xenial, about 80% of the time when I dock my
  thinkpad laptop I get a complete system freeze. The symptoms of the
  freeze are:

   * The two external monitors connected to the dock seem to be in a
  half-configured state - they're powered on, and display some graphics
  from my desktop, but do not yet show the correct contents.

   * I can't get to a console with Ctrl+Alt+F1.

   * I can't kill X with Ctrl+Alt+Backspace

   * I can't get the mouse cursor to appear or move, either with the
  trackpad or the external mouse.

   * Undocking the laptop doesn't help.

  The only thing I *can* do at this point is to hold down the power
  button.

  I seem to recall similar issues in the past (perhaps in Vivid?), where
  the fix ended up being in the graphics driver.

  The laptop is a T540p. The docking station is an "ultra dock pro" -
  not a USB dock, but rather one of those ones where the laoptop clicks
  into a base.

  This bug makes the docking station rather useless, and makes me sad :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thomi  3196 F pulseaudio
   /dev/snd/controlC0:  thomi  3196 F pulseaudio
   /dev/snd/controlC1:  thomi  3196 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 07:35:58 2016
  HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb
  InstallationDate: Installed on 2015-10-12 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575334/+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 1775772] Re: Atheros Wireless ath9k random segmentation fault ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common]

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

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

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

Title:
  Atheros Wireless ath9k random segmentation fault
  ath9k_cmn_rx_skb_postprocess+0x4b/0x130 [ath9k_common]

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello, I got random segmentation fault on my Wireless card Atheros QCA9565 / 
AR9565 here I also attached dmesg and another logs.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CRDA:
   global
   country 98: DFS-UNSET
(2402 - 2472 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-14 (64 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20369
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (50 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G40-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20369
  dmi.product.version: Lenovo G40-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775772/+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 1823706] Re: Sequence of main, restriced, multiverse, universe in the source.list has been changed

2019-04-08 Thread Po-Hsu Lin
For kernel-testing, fix has been pushed here:
https://kernel.ubuntu.com/git/ubuntu/kernel-
testing.git/commit/?id=540a6936fe4adc654e3f3caddec705e38a1f1963

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => High

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   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/1823706

Title:
  Sequence of main, restriced, multiverse, universe in the source.list
  has been changed

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From this cycle, I saw some system got their source.list in this way:
deb http://archive.ubuntu.com/ubuntu trusty universe multiverse main 
restricted

  Not the way it used to be:
deb http://archive.ubuntu.com/ubuntu trusty main restricted multiverse 
universe

  Reporting this as it is the first time that I saw this.

  And we're using "trusty main" as a key to enable the proposed pocket,
  this issue is causing some trouble for our automation. (Can be fixed
  from our tool easily though)

  Also it's noteworthy that this seems to be a bit random. Sometime it
  will act like this but sometimes it will just like the old days.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-168-generic 3.13.0-168.218
  ProcVersionSignature: User Name 3.13.0-168.218-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-168-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  8 11:42 seq
   crw-rw 1 root audio 116, 33 Apr  8 11:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [   48.898467] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Mon Apr  8 11:45:07 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-168-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro console=ttyS0,1152008n1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-168-generic N/A
   linux-backports-modules-3.13.0-168-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1823706/+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 1819786] Re: 4.15 kernel ip_vs --ops causes performance and hang problem

2019-04-08 Thread Marc Hasson
Well, my apologies.   I retract my skepticism!   Your referenced -47
kernel above appears to have fixed the problem, while the stock -47
kernel showed the failure when I tested it this evening first (I already
had the distributed 4.15.0-47 kernel installed, then I removed it and
installed your references).

So, we will be looking forward to the official rollout of this fix.  But
even more important to us is the Xenial 4.15 kernel version, since it is
more widely distributed, as referenced in:

https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1817247

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

Title:
  4.15 kernel ip_vs --ops causes performance and hang problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On our 16.04LTS (and earlier) systems we used the ipvsadm --ops UDP
  support (one-packet scheduling) to get a better distribution amongst
  our real servers behind the load-balancer for some small subset of
  applications.

  This has worked fine through the 4.4.0-xxx kernels. But when we started
  a program to upgrade systems to use the 4.15 series of kernels to take
  advantage of new facilities, the subset of systems which used the --ops
  option ran into problems. Everything else with the 4.15 kernels appeared
  to work well.

  This issue was reported in #1817247 against 16.04LTS with the HWE 4.15 kernel
  but has not received any acknowledgement after having been reported weeks
  ago.   So we have moved on to confirm that a stock 18.04LTS system with the
  latest expected/standard 4.15 kernel also has this issue as well and report
  that here.  Perhaps this will get more attention.

  The issue appears to have been the change in the ip_vs module from using
  "atomic_*()" increment/decrement functions in the 4.4 kernel to instead
  use "refcount_*()" functions in a later kernel, including the 4.15 one
  we switched to. Unfortunately, the simple refcount_dec() function was
  inadequate, in putting out a time-consuming message and handling when
  the refcount dropped to zero, which is expected in the case of --ops
  support that retains no state post packet delivery. I will upload an
  attachment with the sample messages that get put out at packet arrival
  rate, which destroys performance of course. This test VM reports the
  identical errors we see in our production servers, but at least throwing
  only a couple of test --ops packets at it doesn't crash/hang the 18.04 system
  as it did in the 16.04 VM reported earlier.   And in production, with the
  far greater packet rates, our systems fail since the attached call backtrace
  *** appears on every packet!! ***

  This issue was apparently already recognized as an error and has appeared
  as a fix in upstream kernels. This is a reference to the 4.17 version
  of the fix that we'd like to see incorporated into the next possible
  kernel maintenance release:

  
https://github.com/torvalds/linux/commit/a050d345cef0dc6249263540da1e902bba617e43
  #diff-75923493f6e3f314b196a8223b0d6342

  We have successfully used the livepatch facility to build a livepatch .ko
  with the above diffs on our 4.15.0-36 system and successfully demonstrated
  the contrast in good/bad behavior with/without the livepatch module
  loaded. But we'd rather not have to build a version of livepatch.ko for
  each kernel maintenance release, such as the 4.5.0-46 kernel here used to
  demonstrate the issue persists in the Ubuntu mainline distro.

  The problem is easy to generate, with only a couple of packets
  and a simple configuration. Here's a very basic test (addresses
  rewritten/obscured) version of an example configuration for 2 servers
  that worked on my test VM:

  ipvsadm -A -f 100 -s rr --ops
  ipvsadm -a -f 100 -r 10.129.131.227:0 -g -w 
  ipvsadm -a -f 100 -r 10.129.131.228:0 -g -w 
  iptables -t mangle -A PREROUTING -d 172.16.5.1/32 -j MARK --set-xmark 
0x64/0x
  ifconfig lo:0 172.16.5.1/32 up

  Routing and addressing to achieve the above, or adaptation for one's
  own test environment, is left to the tester.  I just added alias 10.129.131.x
  addresses on my "outbound" interface and a static route for 172.16.5.1 to my
  client system so the test packets arrived on the "inbound" interface.

  I set up routing and addresses on my 2 NIC test such that packets arrived
  on my test machine's eth1 NIC and were directed by ip_vs out the eth2. To
  test, all I did was throw a few UDP packets via traceroute at the address
  on the iptables/firewall mark rule so that the eth1 interface of the
  test system was the traceroute system's default gateway:

traceroute -m 2 172.16.5.1

  Without the fix my test ip_vs system either hangs or puts out messages
  as per the attached. With our livepatch module using the above commit's
  contents, all is well. Both of the test ("real" as opposed to "virtual")
  

[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
** Description changed:

- The following commit was requested in the 18.04 Bionic kernel for Azure:
+ The following commit is requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic
  
  This commit was included when it was requested in bug 1805304.  However,
  the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel
  at that time.  The patch was applied to the 4.15 based kernel as an
  Ubuntu SAUCE patch.
  
  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of v4.20-rc6.
  The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that
  point.  Due to this, the patch never made it into any 4.18 kernels,
  which is why it is now missing from 18.04, it was rebased to 4.18.
  
- 
- This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.
+ This is a critical issue.  The 4.18.0-1015 kernel immediately panics on
+ boot without this commit.

** Description changed:

- The following commit is requested in the 18.04 Bionic kernel for Azure:
+ The following commit is being requested in the 18.04 4.18 based Bionic kernel 
for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic
  
  This commit was included when it was requested in bug 1805304.  However,
  the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel
  at that time.  The patch was applied to the 4.15 based kernel as an
  Ubuntu SAUCE patch.
  
  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of v4.20-rc6.
  The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that
  point.  Due to this, the patch never made it into any 4.18 kernels,
  which is why it is now missing from 18.04, it was rebased to 4.18.
  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on
  boot without this commit.

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit is being requested in the 18.04 4.18 based Bionic kernel 
for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  This is a critical issue.  The 4.18.0-1015 kernel immediately panics
  on boot without this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+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 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
And looking a little further, commit ae6935ed7d42(Bionic commit
c40598d9e67c) was added per bug 1812123 for DPDK.  In that bug, we
requested two commits:

b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

However, commit b5679cebf780 is a fix for commit ae6935ed7d42, so commit
ae6935ed7d42 was also included.  That then led to this bug, because with
commit ae6935ed7d42, commit c967590457ca is now also needed.

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit was requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+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 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but

2019-04-08 Thread Daniel van Vugt
** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=110359
   Importance: Unknown
   Status: Unknown

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

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 4.19.26 and later (but 4.19.25 and earlier works)

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

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1822441/+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 1819023] Re: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen

2019-04-08 Thread Daniel van Vugt
I wouldn't expect the setting to be remembered across reboots, but it is
a setting on the graphics card, so maybe it is remembered?...

Also, I don't think "off" is a default that we should ever aim for.
Upstream would probably reject that because for many types of monitor
"off" will look worse.

Did "static 2x2" work for you? I am assuming the problem was "auto"
defaulting to "dynamic 2x2".

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

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

Title:
  [nouveau] Scrolling screen flicker, especially on default Ubuntu lock
  screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My screen is experiencing a weird "scrolling" flicker, especially
  while displaying blue, indigo, and violet hues/colors, such as on the
  default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker
  scrolls up and down, with the brightest part of the flicker being
  towards the top, with a gradient that fades back to the original color
  near the bottom.

  Problem occurs on any one monitor on any one video output protocol
  (DVI-D, HDMI, and VGA).

  
  I will upload an illustration or render as soon as possible for better 
explanation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 10:39:50 2019
  DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
  InstallationDate: Installed on 2018-08-17 (202 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: BIOSTAR Group A880G+
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A880G+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A880G+
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819023/+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 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_scr

2019-04-08 Thread Daniel van Vugt
I'm setting the Nvidia driver to Won't Fix. Not just because we can't
fix those ourselves, but also the bug of reporting a GPU with no CRTCs
is not going to be a bug for other Nvidia card types (pure compute cards
with no graphics outputs). So it's a situation mutter needs to handle
anyway.


** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: nvidia-graphics-drivers-410 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT
  "assertion failed: (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  
  WORKAROUNDS

  Don't use kernel parameter nvidia-drm.modeset=1

  - or -

  Before trying to log in:

  1. Ctrl+Alt+F4, log in to VT4 and run:

 sudo Xorg :4 vt4

  2. Ctrl+Alt+F1, wait for the log screen to reappear, then log in
  normally.

  
  ORIGINAL DESCRIPTION

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+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 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
The reason this missing commit is now causing a panic is because it
Fixes the following commit, which is added by 4.18.0-1015:

c40598d9e67c vmbus: split ring buffer allocation from open

git describe --contains c40598d9e67c
Ubuntu-azure-4.18.0-1015.15_18.04.1~57

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit was requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+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 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1822812
- phase: Holding before Promote to Proposed
- phase-changed: Monday, 08. April 2019 22:42 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 09. April 2019 01:42 UTC
  reason:
-   promote-to-proposed: Holding -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1822812
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 09. April 2019 01:42 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

2019-04-08 Thread Darin Miller
Sound is still working today with the 4.20.17 kernel.  I will give it
another day before I draw any conclusions.

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1809843] Re: sky2 ethernet card link not up after suspend

2019-04-08 Thread Mike Boruta
I have attempted to test the kernel mentioned above and have not been
able to; I enabled the given repo, installed the packages linux-
image-5.0.0-8-generic, linux-headers-5.0.0-8, linux-
headers-5.0.0-8-generic and linux-modules-5.0.0-8-generic and upon
reboot was not able to start gdm. Fine, my nvidia modules failed to
recompile for the new kernel, but when attempting to start networking I
found that the sky2 kernel module was not present on my system. Indeed,
linux-modules-5.0.0-8-generic does not contain sky2, even though it is
built as a module according to the kernel config. Am I missing
something? How do you suggest I test these changes?

Also, why is this titled 'verification-needed-xenial' and not
'verification-needed-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/1809843

Title:
  sky2 ethernet card link not up after suspend

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

Bug description:
  Issue is as described by the user 'kris' in #1798921
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921).

  Sometimes when bringing my laptop up from suspended state my Ethernet
  card shows link connection and activity via port LEDs but ethtool
  indicates the link is not up. This does not happen every time I resume
  from suspend, about one in 5 times. When it does happen, the following
  additional message is present in my dmesg output:

  [  686.804877] do_IRQ: 1.37 No irq handler for vector

  
  The lspci -vvnn output for the Ethernet card is:

  02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8057 
PCI-E Gigabit Ethernet Controller [11ab:4380] (rev 10)
Subsystem: Acer Incorporated [ALI] 88E8057 PCI-E Gigabit Ethernet 
Controller [1025:028e]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/34, in 
the hopes that this specific card will be added to the relevant MSI quirks 
table. If I do not suffer from the same issue as kris in the above linked 
issue, I will be happy to provide any additional information, test fixes etc. I 
would like to avoid using the 'pci=nomsi,noaer' workaround he mentioned if 
possible.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   maridius   2260 F...m pulseaudio
   /dev/snd/controlC0:  maridius   2260 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=0840edd3-6052-4916-bcc2-4c5b13edb862
  InstallationDate: Installed on 2015-09-01 (1212 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gateway P-79
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=ad05ff21-9786-4f03-8641-85f2f416363d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45+PHC-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/30/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 79.07.00
  dmi.board.name: Godzilla-N10
  dmi.board.vendor: Gateway
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr79.07.00:bd09/30/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A:
  dmi.product.name: P-79
  dmi.product.version: 0100
  dmi.sys.vendor: Gateway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+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 1823819] Re: Upgrade to 19.04 fails with linux-image-5.0.0-8

2019-04-08 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1823819

** Tags added: iso-testing

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

Title:
  Upgrade to 19.04 fails with linux-image-5.0.0-8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrade to 19.04 Ubuntu MATE fails with following:

  Could not install 'linux-image-5.0.0-8-generic
  triggers looping, abandoned

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  Same error as Bug #1823116

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testdev1634 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr  8 18:22:14 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=f20f596d-9e53-4bb6-bf4a-df5764d8ddb2 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-09 (0 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823819/+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 1823819] Status changed to Confirmed

2019-04-08 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Upgrade to 19.04 fails with linux-image-5.0.0-8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrade to 19.04 Ubuntu MATE fails with following:

  Could not install 'linux-image-5.0.0-8-generic
  triggers looping, abandoned

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  Same error as Bug #1823116

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testdev1634 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr  8 18:22:14 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=f20f596d-9e53-4bb6-bf4a-df5764d8ddb2 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-09 (0 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823819/+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 1819786] Re: 4.15 kernel ip_vs --ops causes performance and hang problem

2019-04-08 Thread Marc Hasson
Thanks for getting back to me on this.  Sorry for the slow response, did not 
get (or see?) an email notification about an update.

I'll try the -47 kernel you referenced but I'm skeptical since the
failure occurs on the -46 and the -47 doesn't show any changelog for the
ipvs refcount issue.  Nor does the -47 source I downloaded from Ubuntu
show the fix.

But on the off-chance that you're just asking to confirm to test the
latest, or that you included the fix below in the kernel you referenced
even though its named identically to the kernel we received last month,
I'll give it a try and let you know.

Again, for reference, the upstream fix/patch we are requesting for both
this launchpad report as well as
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1817247
is as follows:

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


I'll let you know the results of testing this latest -47.   And I presume I'll 
have the -48 shortly as well, that one's changelog also gives no indication of 
having the fix yet.

Thanks.

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

Title:
  4.15 kernel ip_vs --ops causes performance and hang problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On our 16.04LTS (and earlier) systems we used the ipvsadm --ops UDP
  support (one-packet scheduling) to get a better distribution amongst
  our real servers behind the load-balancer for some small subset of
  applications.

  This has worked fine through the 4.4.0-xxx kernels. But when we started
  a program to upgrade systems to use the 4.15 series of kernels to take
  advantage of new facilities, the subset of systems which used the --ops
  option ran into problems. Everything else with the 4.15 kernels appeared
  to work well.

  This issue was reported in #1817247 against 16.04LTS with the HWE 4.15 kernel
  but has not received any acknowledgement after having been reported weeks
  ago.   So we have moved on to confirm that a stock 18.04LTS system with the
  latest expected/standard 4.15 kernel also has this issue as well and report
  that here.  Perhaps this will get more attention.

  The issue appears to have been the change in the ip_vs module from using
  "atomic_*()" increment/decrement functions in the 4.4 kernel to instead
  use "refcount_*()" functions in a later kernel, including the 4.15 one
  we switched to. Unfortunately, the simple refcount_dec() function was
  inadequate, in putting out a time-consuming message and handling when
  the refcount dropped to zero, which is expected in the case of --ops
  support that retains no state post packet delivery. I will upload an
  attachment with the sample messages that get put out at packet arrival
  rate, which destroys performance of course. This test VM reports the
  identical errors we see in our production servers, but at least throwing
  only a couple of test --ops packets at it doesn't crash/hang the 18.04 system
  as it did in the 16.04 VM reported earlier.   And in production, with the
  far greater packet rates, our systems fail since the attached call backtrace
  *** appears on every packet!! ***

  This issue was apparently already recognized as an error and has appeared
  as a fix in upstream kernels. This is a reference to the 4.17 version
  of the fix that we'd like to see incorporated into the next possible
  kernel maintenance release:

  
https://github.com/torvalds/linux/commit/a050d345cef0dc6249263540da1e902bba617e43
  #diff-75923493f6e3f314b196a8223b0d6342

  We have successfully used the livepatch facility to build a livepatch .ko
  with the above diffs on our 4.15.0-36 system and successfully demonstrated
  the contrast in good/bad behavior with/without the livepatch module
  loaded. But we'd rather not have to build a version of livepatch.ko for
  each kernel maintenance release, such as the 4.5.0-46 kernel here used to
  demonstrate the issue persists in the Ubuntu mainline distro.

  The problem is easy to generate, with only a couple of packets
  and a simple configuration. Here's a very basic test (addresses
  rewritten/obscured) version of an example configuration for 2 servers
  that worked on my test VM:

  ipvsadm -A -f 100 -s rr --ops
  ipvsadm -a -f 100 -r 10.129.131.227:0 -g -w 
  ipvsadm -a -f 100 -r 10.129.131.228:0 -g -w 
  iptables -t mangle -A PREROUTING -d 172.16.5.1/32 -j MARK --set-xmark 
0x64/0x
  ifconfig lo:0 172.16.5.1/32 up

  Routing and addressing to achieve the above, or adaptation for one's
  own test environment, is left to the tester.  I just added alias 10.129.131.x
  addresses on my "outbound" interface and a static route for 172.16.5.1 to my
  client system so the test packets arrived on the "inbound" interface.

  I set up routing and addresses on my 2 NIC test such that packets 

[Kernel-packages] [Bug 1823819] [NEW] Upgrade to 19.04 fails with linux-image-5.0.0-8

2019-04-08 Thread FranksMCB
Public bug reported:

Upgrade to 19.04 Ubuntu MATE fails with following:

Could not install 'linux-image-5.0.0-8-generic
triggers looping, abandoned

Could not install the upgrades

The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).

Same error as Bug #1823116

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-8-generic 5.0.0-8.9
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu25
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  testdev1634 F pulseaudio
CurrentDesktop: MATE
Date: Mon Apr  8 18:22:14 2019
InstallationDate: Installed on 2019-04-08 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
IwConfig:
 lono wireless extensions.
 
 ens33 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=f20f596d-9e53-4bb6-bf4a-df5764d8ddb2 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-8-generic N/A
 linux-backports-modules-5.0.0-8-generic  N/A
 linux-firmware   1.178
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-04-09 (0 days ago)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug disco

** Attachment added: "error.tar.gz"
   
https://bugs.launchpad.net/bugs/1823819/+attachment/5254350/+files/error.tar.gz

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

Title:
  Upgrade to 19.04 fails with linux-image-5.0.0-8

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrade to 19.04 Ubuntu MATE fails with following:

  Could not install 'linux-image-5.0.0-8-generic
  triggers looping, abandoned

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  Same error as Bug #1823116

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testdev1634 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr  8 18:22:14 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=f20f596d-9e53-4bb6-bf4a-df5764d8ddb2 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-09 (0 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix 

[Kernel-packages] [Bug 1332824] Re: [Samsung XE700T1C-A01FR] Smartpad not properly recognised

2019-04-08 Thread Ahmed
Bug still exists for ubuntu 18.10

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

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

Title:
  [Samsung XE700T1C-A01FR] Smartpad not properly recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expecting at least the smartpad to be properly recognised with the
  bare minimum multi-touch gesture: two-fingers right click, side
  scrolling, two-fingers scrolling, mouse speed.

  xinput -list gives:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Wacom ISDv4 EC Pen stylus   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Atmel Atmel maXTouch Digitizer  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ USB Keyboard+SmartPad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ Wacom ISDv4 EC Pen eraser   id=16   [slave  pointer 
 (2)]
  ⎜   ↳ Asus gaming Mouse (G112)id=19   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ WebCam SC-50AFL11C54N   id=11   [slave  
keyboard (3)]
  ↳ USB Keyboard+SmartPad   id=12   [slave  
keyboard (3)]
  ↳ WebCam SC-20HDM12347N   id=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=15   [slave  
keyboard (3)]
  ↳ Chicony USB Keyboardid=17   [slave  
keyboard (3)]
  ↳ Chicony USB Keyboardid=18   [slave  
keyboard (3)]
  ↳ Acer Crystal Eye Webcam id=20   [slave  
keyboard (3)]

  Note that "USB Keyboard+SmartPad" is present twice (id 12 and 13)

  Also note that running
   xinput test 13
  doesn't detect any multitouch on the smartpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 21 15:52:14 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
  InstallationDate: Installed on 2014-06-18 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=1fdb1c66-705c-4c1a-8d6c-d363ad0e53b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P10AAT.050.140215.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: XE700T1C-A01FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
  dmi.product.name: 700T1C
  dmi.product.version: P10AAT
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1822812
- phase: Packaging
- phase-changed: Monday, 08. April 2019 18:42 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Monday, 08. April 2019 22:42 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Holding -- builds not complete

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

Title:
  linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1822812
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 08. April 2019 22:42 UTC
  reason:
promote-to-proposed: Holding -- builds not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+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 1823805] [NEW] The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
Public bug reported:

The following commit was requested in the 18.04 Bionic kernel for Azure:
c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

This commit was included when it was requested in bug 1805304.  However,
the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel
at that time.  The patch was applied to the 4.15 based kernel as an
Ubuntu SAUCE patch.

The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
kernel.  This requested commit was applied to mainline as of v4.20-rc6.
The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that
point.  Due to this, the patch never made it into any 4.18 kernels,
which is why it is now missing from 18.04, it was rebased to 4.18.


This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

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


** Tags: kernel-hyper-v kernel-key

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit was requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+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

2019-04-08 Thread Gordon Dracup
Is this issue fixed in 4.18.0-17-generic #18~18.04.1-Ubuntu SMP Fri Mar
15 15:27:12 UTC 2019?

I have just done a fresh install. Modprobe workaround doesn't seem to
work. Happy to provide any information required.

gordon:~$ sudo lshw -C network
 
  *-network 
   description: Wireless interface
   product: Wireless 7260
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:02:00.0
   logical name: wlp2s0
   version: 73
   serial: 0c:8b:fd:48:fe:40
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.18.0-17-generic firmware=17.948900127.0 ip=192.168.69.113 
latency=0 link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:46 memory:e350-e3501fff
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0.1
   bus info: pci@:03:00.1
   logical name: enp3s0f1
   version: 12
   serial: 78:45:c4:c9:4e:61
   size: 10Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-2_0.0.1 07/08/13 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
   resources: irq:19 ioport:4000(size=256) memory:e3404000-e3404fff 
memory:e340-e3403fff

-- 
You 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:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

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 

[Kernel-packages] [Bug 1821383] Re: synaptics touchpoint fails after resume

2019-04-08 Thread Pedro Côrte-Real
** Attachment added: "dmesg output right after initial boot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821383/+attachment/5254295/+files/initial_dmesg

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

Title:
  synaptics touchpoint fails after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To workaround bug #924648 I've installed the following:

  $ cat /etc/udev/rules.d/10-trackpoint.rules 
  ACTION=="add|change",
  SUBSYSTEM=="input",
  ATTR{name}=="TPPS/2 IBM TrackPoint",
  ATTR{device/sensitivity}="250",
  ATTR{device/speed}="250",

  While this works I now sometimes get a broken pointer after suspend.
  dmesg shows this at resume:

  [353671.884852] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [353672.381746] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [353672.845761] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  After some time it resets and the pointer is back. Most of the time
  just this is shown:

  [353852.538962] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [353852.735990] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input52

  But I did get a timeout call trace once:

  [ 5676.512616] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0
  [ 5677.453153] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [ 5677.643970] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input21
  [ 5800.035392] INFO: task kworker/0:2:9739 blocked for more than 120 seconds.
  [ 5800.035402]   Tainted: G   OE4.15.0-45-generic #48-Ubuntu
  [ 5800.035406] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5800.035410] kworker/0:2 D0  9739  2 0x8000
  [ 5800.035424] Workqueue: events_long serio_handle_event
  [ 5800.035427] Call Trace:
  [ 5800.035439]  __schedule+0x291/0x8a0
  [ 5800.035445]  ? schedule_timeout+0x165/0x350
  [ 5800.035453]  schedule+0x2c/0x80
  [ 5800.035460]  __kernfs_remove.part.12+0x175/0x1f0
  [ 5800.035467]  ? wait_woken+0x80/0x80
  [ 5800.035474]  kernfs_remove_by_name_ns+0x54/0xa0
  [ 5800.035479]  remove_files.isra.1+0x35/0x70
  [ 5800.035484]  sysfs_remove_group+0x44/0x90
  [ 5800.035488]  sysfs_remove_groups+0x2e/0x50
  [ 5800.035493]  device_remove_groups+0x12/0x20
  [ 5800.035508]  trackpoint_disconnect+0x44/0x70 [psmouse]
  [ 5800.035517]  psmouse_disconnect+0xfe/0x190 [psmouse]
  [ 5800.035525]  serio_disconnect_driver+0x36/0x50
  [ 5800.035531]  serio_driver_remove+0x15/0x20
  [ 5800.035539]  device_release_driver_internal+0x15b/0x240
  [ 5800.035544]  device_release_driver+0x12/0x20
  [ 5800.035548]  serio_disconnect_port+0x98/0xb0
  [ 5800.035553]  serio_handle_event+0x18e/0x250
  [ 5800.035559]  process_one_work+0x1de/0x410
  [ 5800.035565]  worker_thread+0x32/0x410
  [ 5800.035572]  kthread+0x121/0x140
  [ 5800.035576]  ? process_one_work+0x410/0x410
  [ 5800.035582]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 5800.035589]  ? do_syscall_64+0x73/0x130
  [ 5800.035594]  ? SyS_exit+0x17/0x20
  [ 5800.035600]  ret_from_fork+0x35/0x40
  [ 5858.636930] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [ 5858.872453] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input22

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   26606 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:20:56 2019
  InstallationDate: Installed on 2018-05-31 (295 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 5986:0706 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FAS5TS00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=0206141b-5758-4895-bbbd-8022b1e78519 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-04-08 Thread Brian Wharton
I have the same problem on my Vostro 3500. I'm using the
4.15.0-47-generic kernel with Gnome 3.28.2 on 18.04.2 LTS. Temperatures
are at 67-81C and using Win10 on the same laptop the temperatures are
45-57C with no apps running in either OS.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot

2019-04-08 Thread dann frazier
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1667490] Comment bridged from LTC Bugzilla

2019-04-08 Thread bugproxy
--- Comment From s...@us.ibm.com 2019-04-08 15:54 EDT---
What is the next step?

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

Title:
  Please disable unnecessary config options in the Ubuntu 17.04 kernel
  config

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Some krnel config options for IMA should not be enabled in the Ubuntu 17.04 
kernel as they are at best experimental and at worst dangerous:

CONFIG_IMA_APPRAISE_SIGNED_INIT
CONFIG_IMA_BLACKLIST_KEYRING
CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY
CONFIG_IIMA_READ_POLICY
CONFIG_IIMA_WRITE_POLICY

  Please disable these config options in the Ubuntu 17.04 kernel config.
   
  ---uname output---
  Linux briggs-rtp-2 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = S822LC 8001-22C

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667490/+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 1008400] Re: Ubuntu server uses CFQ scheduler instead of deadline

2019-04-08 Thread Bjoern Teipel
In my opinion I also agree to use deadline scheduler for server kernel
which is also the same problem on the 4.15 kernel, if a server kernel
would still exist.

Under trusty we generally saw good performance with deadline scheduler and on a 
recent SSD based deployment with 4.15 I noticed a large performance regression 
for random IO until we reverted to deadline. You could argue that the scheduler 
can be changed at any time but on the contrary I would assume more general 
suitable parameters from a server distro vs a desktop distro.
My larger problem is that this change was seemingly done via 
https://kernel.ubuntu.com/git/ubuntu/ubuntu-zesty.git/commit/?id=af80b83a2b6184fea27f050948146fcd9a28070d
 by a test based on kernel compiles etc, which to be honest, is not a standard 
server use case. Apart from the issue that I could not spot any documentation 
on the release notes that this has changed. If this has been documented and 
simply missed it, then please ignore this comment. But now I'm wondering what 
else has changed now.

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

Title:
  Ubuntu server uses CFQ scheduler instead of deadline

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Ubuntu server now uses the '-generic' kernel, as the '-server' kernel
  doesn't exist anymore. With this change the default server disk
  scheduler changed from deadline to CFQ. This is very bad for servers,
  deadline should absolutely be the default for servers.

  For example we moved some KVM images to an Ubuntu 12.04 server, but we
  had to revert as we got lots of disk errors and eventually frozen
  disks on these KVM's due to write timeouts. It took us a while before
  we found out that this 12.04 server used CFQ, which surprised us a
  lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1008400/+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 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_scr

2019-04-08 Thread Treviño
** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT
  "assertion failed: (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  
  WORKAROUNDS

  Don't use kernel parameter nvidia-drm.modeset=1

  - or -

  Before trying to log in:

  1. Ctrl+Alt+F4, log in to VT4 and run:

 sudo Xorg :4 vt4

  2. Ctrl+Alt+F1, wait for the log screen to reappear, then log in
  normally.

  
  ORIGINAL DESCRIPTION

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+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 1823780] Status changed to Confirmed

2019-04-08 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Touchpad stopped working suddenly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have dual boot with windows from year.The touchpad has been working
  fine till now but it stopped working suddenly.It still works on
  windows though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nsk06  2240 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 05:36:08 2019
  HibernationDevice: RESUME=UUID=c854a58f-a6c2-4f17-bb97-7a7456960278
  InstallationDate: Installed on 2018-03-19 (385 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP ENVY x360 Convertible 15m-bp1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=81ecfc7a-2ce4-48da-a626-08c07c96a86d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-06 (245 days ago)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83C8
  dmi.board.vendor: HP
  dmi.board.version: 32.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPENVYx360Convertible15m-bp1xx:pvrType1ProductConfigId:rvnHP:rn83C8:rvr32.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bp1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823780/+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 1823753] Re: arm64: cma_alloc errors at boot

2019-04-08 Thread dann frazier
I enabled CMA_DEBUG & CMA_DEBUGFS and booted w/ cma=128M so that we can
see the CMA state when no allocations fail.

root@d06-4:/sys/kernel/debug/cma/cma-reserved# cat count 
32768
root@d06-4:/sys/kernel/debug/cma/cma-reserved# cat used 
15630

Looks like we're actually using ~61M - and perhaps the alignment
requirements are pushing us over the 64M barrier (cma=64M still results
in some cma_alloc failures).

** Attachment added: "dmesg w/ CMA_DEBUG=y"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+attachment/5254279/+files/dmesg-cma-debug.txt

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1823780] Status changed to Confirmed

2019-04-08 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

Title:
  Touchpad stopped working suddenly

Status in linux package in Ubuntu:
  New

Bug description:
  I have dual boot with windows from year.The touchpad has been working
  fine till now but it stopped working suddenly.It still works on
  windows though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nsk06  2240 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 05:36:08 2019
  HibernationDevice: RESUME=UUID=c854a58f-a6c2-4f17-bb97-7a7456960278
  InstallationDate: Installed on 2018-03-19 (385 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP ENVY x360 Convertible 15m-bp1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=81ecfc7a-2ce4-48da-a626-08c07c96a86d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-06 (245 days ago)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83C8
  dmi.board.vendor: HP
  dmi.board.version: 32.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPENVYx360Convertible15m-bp1xx:pvrType1ProductConfigId:rvnHP:rn83C8:rvr32.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bp1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823780/+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 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Invalid

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1822812
- phase: Ready for Packaging
- phase-changed: Thursday, 04. April 2019 14:54 UTC
+ phase: Packaging
+ phase-changed: Monday, 08. April 2019 18:42 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1822812
  phase: Packaging
  phase-changed: Monday, 08. April 2019 18:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+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 1823780] [NEW] Touchpad stopped working suddenly

2019-04-08 Thread nonidh singh
Public bug reported:

I have dual boot with windows from year.The touchpad has been working
fine till now but it stopped working suddenly.It still works on windows
though.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-47-generic 4.15.0-47.50
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nsk06  2240 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 05:36:08 2019
HibernationDevice: RESUME=UUID=c854a58f-a6c2-4f17-bb97-7a7456960278
InstallationDate: Installed on 2018-03-19 (385 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: HP HP ENVY x360 Convertible 15m-bp1xx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=81ecfc7a-2ce4-48da-a626-08c07c96a86d ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-47-generic N/A
 linux-backports-modules-4.15.0-47-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-06 (245 days ago)
dmi.bios.date: 07/24/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83C8
dmi.board.vendor: HP
dmi.board.version: 32.60
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPENVYx360Convertible15m-bp1xx:pvrType1ProductConfigId:rvnHP:rn83C8:rvr32.60:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 15m-bp1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug bionic

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

Title:
  Touchpad stopped working suddenly

Status in linux package in Ubuntu:
  New

Bug description:
  I have dual boot with windows from year.The touchpad has been working
  fine till now but it stopped working suddenly.It still works on
  windows though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-47-generic 4.15.0-47.50
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nsk06  2240 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 05:36:08 2019
  HibernationDevice: RESUME=UUID=c854a58f-a6c2-4f17-bb97-7a7456960278
  InstallationDate: Installed on 2018-03-19 (385 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP ENVY x360 Convertible 15m-bp1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=81ecfc7a-2ce4-48da-a626-08c07c96a86d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-06 (245 days ago)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83C8
  dmi.board.vendor: HP
  dmi.board.version: 32.60
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPENVYx360Convertible15m-bp1xx:pvrType1ProductConfigId:rvnHP:rn83C8:rvr32.60:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bp1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823780/+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 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but

2019-04-08 Thread Torsten Römer
Done: https://bugs.freedesktop.org/show_bug.cgi?id=110359

Thanks to all helping out!

** Bug watch added: freedesktop.org Bugzilla #110359
   https://bugs.freedesktop.org/show_bug.cgi?id=110359

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

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 4.19.26 and later (but 4.19.25 and earlier works)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+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 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

2019-04-08 Thread Kleber Sacilotto de Souza
** Summary changed:

- linux-oracle:  -proposed tracker
+ linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1822812
  phase: Ready for Packaging
  phase-changed: Thursday, 04. April 2019 14:54 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+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 1821882] Re: Screen is very dark and brightness cannot be adjusted

2019-04-08 Thread Kai-Heng Feng
I tried _BCM for both its ACPI graphics devices, and it doesn't work
whether "Enable Switchable Graphics" is enabled or not. So for this
platform, the brightness is not controlled by its ACPI interface.

The nouveau backlight in use is nva3_bl_ops. Both its callback
nva3_get_intensity() and nva3_set_intensity() correctly gets called by
.get_brightness and .update_status, respectively.

The proprietary Nvidia driver registered "nvidia_0" in backlight sysfs
and it can adjust brightness correctly. Skimming through its kernel
source, the backlight is set by rm_set_backlight() which resides in the
binary blob. Seems like we need to reverse engineer this to make it work
under nouveau.

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287867] ACPI Error: 

[Kernel-packages] [Bug 1823754] Re: Set CONFIG_RANDOM_TRUST_CPU=y

2019-04-08 Thread Seth Forshee
** Changed in: linux-aws (Ubuntu)
   Status: In Progress => Fix Committed

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

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

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

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

Title:
  Set CONFIG_RANDOM_TRUST_CPU=y

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux-kvm package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Turning this option on will make our kernels by default trust
  the CPU's random number generator for the purpose of initializing the
  kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at
  boot time by passing random.trust_cpu=off. Turning this on has the
  potential to prevent getrandom(2) from blocking during early boot.
  This option was turned on in the master kernel shortly before disco
  kernel freeze; this bug is about propagating the option to derivative
  kernels.

  Regression Potential: No user-visible regressions are expected. Some
  security-conscious users may prefer to not trust the CPU maker's RNG,
  but in that case the boot options is available.

  Test Case: The benefit is difficult to verify empirically in Ubuntu
  kernels since we carry a patch to avoid problems with getrandom(2)
  blocking immediately following boot. However, it is possible to see
  whether or not the kernel used the CPU RNG for initializing the CRNG
  by searching for the string "random: crng done (trusting CPU's
  manufacturer)" in dmesg.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823754/+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 1818552] Re: disable a.out support

2019-04-08 Thread Tyler Hicks
Adjusting the grep a little to focus on Cosmic, Bionic, and Xenial and
to only match CONFIG_BINFMT_AOUT, I get this:

 $ grep -rl BINFMT_AOUT=[ym] {cosmic,bionic,xenial} | grep -v -e lowlatency -e 
generic
 xenial/linux-hwe/4.8.0-49.52~16.04.1/armel-config.flavour.omap4
 xenial/linux-hwe/4.8.0-49.52~16.04.1/armhf-config.flavour.omap4
 xenial/linux-mako/3.4.0-7.44/i386-config.flavour.virtual
 xenial/linux-hwe-edge/4.10.0-20.22~16.04.1/armel-config.flavour.omap4

I've excluded lowlatency and generic search results because of the bug
mentioned above in comment #4 (we know that the i386 generic kernels
need to be fixed in all releases).

Mako and omap4 HWE kernels are not supported so I don't think there's
anything additional to do outside of updating the i386 generic kernels
in Cosmic, Bionic, and Xenial.

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

Title:
  disable a.out support

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Hello,

  I suggest we disable a.out support in our kernels. It's quite old,
  likely has security problems, and unlikely to have users.

  
  Here's a hand-filtered list of kernel configs that were returned from this 
list:

  grep -rl -e AOUT=m -e AOUT=y | sort -n

  I've selected what looks like the most recent kernels from among:
  precise
  trusty
  xenial
  bionic
  cosmic

  There is no disco because it's not on the kernel.ubuntu.com/kernel-
  config rsync source.

  Thanks

  precise/linux/3.2.0-126.169/i386-config.flavour.generic
  precise/linux/3.2.0-126.169/i386-config.flavour.generic-pae
  precise/linux/3.2.0-126.169/i386-config.flavour.lowlatency
  precise/linux/3.2.0-126.169/i386-config.flavour.virtual
  precise/linux/3.8.0-25.36/armel-config.flavour.omap4
  precise/linux/3.8.0-25.36/armhf-config.flavour.omap4
  precise/linux/3.8.0-25.36/i386-config.flavour.generic
  precise/linux/3.8.0-25.36/i386-config.flavour.lowlatency
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.generic
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.lowlatency
  precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.generic
  
precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.lowlatency
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.generic
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.lowlatency
  trusty/linux/3.13.0-148.197/i386-config.flavour.generic
  trusty/linux/3.13.0-148.197/i386-config.flavour.lowlatency
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.generic
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.lowlatency
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.generic
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.lowlatency
  xenial/linux/4.4.0-125.150/i386-config.flavour.generic
  xenial/linux/4.4.0-125.150/i386-config.flavour.lowlatency
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.generic
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.lowlatency
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.generic
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.lowlatency
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.generic
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.generic
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.23/armhf-config.flavour.flo
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.generic
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.lowlatency
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.generic
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.generic
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1036.36/armhf-config.flavour.mako
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic-pae
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.goldfish
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.lowlatency
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.virtual
  xenial/linux-goldfish/3.4.0-4.27/armhf-config.flavour.goldfish
  xenial/linux-goldfish/3.4.0-4.27/i386-config.flavour.goldfish
  xenial/linux-hwe/4.13.0-42.47~16.04.1/i386-config.flavour.generic
  xenial/linux-hwe/4.13.0-42.47~16.04.1/i386-config.flavour.lowlatency
  xenial/linux-hwe/4.8.0-49.52~16.04.1/armel-config.flavour.omap4
  

[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot

2019-04-08 Thread dann frazier
This was not an issue prior to v4.20. Bisection identified the following commit:
  886643b766321 arm64: use the generic swiotlb_dma_ops

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1823753] Re: arm64: cma_alloc errors at boot

2019-04-08 Thread dann frazier
The disco kernel uses CONFIG_CMA_SIZE_MBYTES=16, while the arm64
defconfig sets it to 32. I tried bumping up this setting by powers of 2
until the messages went away, and it finally did at 128, which seems
extreme. Need to figure out what is attempting these allocations, and
why they are failing.

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1818552] Re: disable a.out support

2019-04-08 Thread Tyler Hicks
Another thing to note is that CONFIG_HAVE_AOUT=y does not indicate that
the a.out binfmt handler is enabled but the grep output in the bug
description does include those matches. For example, the file xenial
/linux-flo/3.4.0-5.23/armhf-config.flavour.flo has these lines:

 CONFIG_HAVE_AOUT=y
 # CONFIG_BINFMT_AOUT is not set

That means that linux-flo for Xenial is not affected by this bug report.

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

Title:
  disable a.out support

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Hello,

  I suggest we disable a.out support in our kernels. It's quite old,
  likely has security problems, and unlikely to have users.

  
  Here's a hand-filtered list of kernel configs that were returned from this 
list:

  grep -rl -e AOUT=m -e AOUT=y | sort -n

  I've selected what looks like the most recent kernels from among:
  precise
  trusty
  xenial
  bionic
  cosmic

  There is no disco because it's not on the kernel.ubuntu.com/kernel-
  config rsync source.

  Thanks

  precise/linux/3.2.0-126.169/i386-config.flavour.generic
  precise/linux/3.2.0-126.169/i386-config.flavour.generic-pae
  precise/linux/3.2.0-126.169/i386-config.flavour.lowlatency
  precise/linux/3.2.0-126.169/i386-config.flavour.virtual
  precise/linux/3.8.0-25.36/armel-config.flavour.omap4
  precise/linux/3.8.0-25.36/armhf-config.flavour.omap4
  precise/linux/3.8.0-25.36/i386-config.flavour.generic
  precise/linux/3.8.0-25.36/i386-config.flavour.lowlatency
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.generic
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.lowlatency
  precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.generic
  
precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.lowlatency
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.generic
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.lowlatency
  trusty/linux/3.13.0-148.197/i386-config.flavour.generic
  trusty/linux/3.13.0-148.197/i386-config.flavour.lowlatency
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.generic
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.lowlatency
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.generic
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.lowlatency
  xenial/linux/4.4.0-125.150/i386-config.flavour.generic
  xenial/linux/4.4.0-125.150/i386-config.flavour.lowlatency
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.generic
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.lowlatency
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.generic
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.lowlatency
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.generic
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.generic
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.23/armhf-config.flavour.flo
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.generic
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.lowlatency
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.generic
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.generic
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1036.36/armhf-config.flavour.mako
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic-pae
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.goldfish
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.lowlatency
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.virtual
  xenial/linux-goldfish/3.4.0-4.27/armhf-config.flavour.goldfish
  xenial/linux-goldfish/3.4.0-4.27/i386-config.flavour.goldfish
  xenial/linux-hwe/4.13.0-42.47~16.04.1/i386-config.flavour.generic
  xenial/linux-hwe/4.13.0-42.47~16.04.1/i386-config.flavour.lowlatency
  xenial/linux-hwe/4.8.0-49.52~16.04.1/armel-config.flavour.omap4
  xenial/linux-hwe/4.8.0-49.52~16.04.1/armhf-config.flavour.omap4
  xenial/linux-hwe/4.8.0-58.63~16.04.1/i386-config.flavour.generic
  xenial/linux-hwe/4.8.0-58.63~16.04.1/i386-config.flavour.lowlatency
  xenial/linux-hwe-edge/4.15.0-21.22~16.04.1/i386-config.flavour.generic
  xenial/linux-hwe-edge/4.15.0-21.22~16.04.1/i386-config.flavour.lowlatency
  xenial/linux-joule/4.4.0-1005.10/i386-config.flavour.generic
  

[Kernel-packages] [Bug 1818552] Re: disable a.out support

2019-04-08 Thread Tyler Hicks
The output from Seth's grep (in the bug description) is a little
misleading because the archival of kernel configs on kernel.ubuntu.com
is buggy. It is including kernel configs of the generic, lowlatency,
etc., kernels in the directories of the derivative kernels. For example,
these config files should not exist because the linux-kvm source package
does not produce an i386 generic or lowlatency binary package:

 cosmic/linux-kvm/4.15.0-1008.8/i386-config.flavour.generic
 cosmic/linux-kvm/4.15.0-1008.8/i386-config.flavour.lowlatency

If we inspect the directory contents while logged into
kernel.ubuntu.com, we see this:

 $ ls -1 ~kernel-ppa/public_html/config/cosmic/linux-kvm/4.15.0-1008.8/
 amd64-config.flavour.generic
 amd64-config.flavour.kvm
 amd64-config.flavour.lowlatency
 arm64-config.flavour.generic
 arm64-config.flavour.snapdragon
 armhf-config.flavour.generic
 armhf-config.flavour.generic-lpae
 i386-config.flavour.generic
 i386-config.flavour.lowlatency
 ppc64el-config.flavour.generic
 s390x-config.flavour.generic

Of those files, only amd64-config.flavour.kvm is valid for linux-kvm and
it does not contain CONFIG_BINFMT_AOUT=m because it is a 64 bit kernel.

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

Title:
  disable a.out support

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Hello,

  I suggest we disable a.out support in our kernels. It's quite old,
  likely has security problems, and unlikely to have users.

  
  Here's a hand-filtered list of kernel configs that were returned from this 
list:

  grep -rl -e AOUT=m -e AOUT=y | sort -n

  I've selected what looks like the most recent kernels from among:
  precise
  trusty
  xenial
  bionic
  cosmic

  There is no disco because it's not on the kernel.ubuntu.com/kernel-
  config rsync source.

  Thanks

  precise/linux/3.2.0-126.169/i386-config.flavour.generic
  precise/linux/3.2.0-126.169/i386-config.flavour.generic-pae
  precise/linux/3.2.0-126.169/i386-config.flavour.lowlatency
  precise/linux/3.2.0-126.169/i386-config.flavour.virtual
  precise/linux/3.8.0-25.36/armel-config.flavour.omap4
  precise/linux/3.8.0-25.36/armhf-config.flavour.omap4
  precise/linux/3.8.0-25.36/i386-config.flavour.generic
  precise/linux/3.8.0-25.36/i386-config.flavour.lowlatency
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.generic
  precise/linux-armadaxp/3.2.0-1687.114/i386-config.flavour.lowlatency
  precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.generic
  
precise/linux-lts-trusty/3.13.0-148.197~precise1/i386-config.flavour.lowlatency
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.generic
  precise/linux-ti-omap4/3.2.0-1504.131/i386-config.flavour.lowlatency
  trusty/linux/3.13.0-148.197/i386-config.flavour.generic
  trusty/linux/3.13.0-148.197/i386-config.flavour.lowlatency
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.generic
  trusty/linux-aws/4.4.0-1004.4/i386-config.flavour.lowlatency
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.generic
  trusty/linux-lts-xenial/4.4.0-125.150~14.04.1/i386-config.flavour.lowlatency
  xenial/linux/4.4.0-125.150/i386-config.flavour.generic
  xenial/linux/4.4.0-125.150/i386-config.flavour.lowlatency
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.generic
  xenial/linux-aws/4.4.0-1055.64/i386-config.flavour.lowlatency
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.generic
  xenial/linux-azure/4.13.0-1001.1/i386-config.flavour.lowlatency
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.generic
  xenial/linux-euclid/4.4.0-9019.20/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.generic
  xenial/linux-flo/3.4.0-5.19/i386-config.flavour.lowlatency
  xenial/linux-flo/3.4.0-5.23/armhf-config.flavour.flo
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.generic
  xenial/linux-gcp/4.10.0-1009.9/i386-config.flavour.lowlatency
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.generic
  xenial/linux-gcp/4.8.0-1002.2/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.generic
  xenial/linux-gke/4.4.0-1034.34/i386-config.flavour.lowlatency
  xenial/linux-gke/4.4.0-1036.36/armhf-config.flavour.mako
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.generic-pae
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.goldfish
  xenial/linux-goldfish/3.4.0-4.26/i386-config.flavour.lowlatency
  

[Kernel-packages] [Bug 1823770] Re: kernel upgrade changes bios boot order

2019-04-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  kernel upgrade changes bios boot order

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a work-laptop which I dual-boot Windows and Ubuntu.

  I need Windows for work, and have that as the default boot option in the bios.
  But after an upgrade of the Ubuntu Linux kernel Ubuntu gets moved to the top 
of the bios boot-order, and Windows gets moved down.

  It doesn't take long to change back, but is a inconvenience. 
  It is a T480s ThinkPad with SecureBoot enabled.

  It has happened before, but I haven't gotten around to reporting it.
  It happened lately with

  cat /proc/version_signature 
  Ubuntu 4.15.0-47.50-generic 4.15.18

  Let me know if you need any other info, and I shall do my best to get
  it to you.

  Cheers, and thanks for your good work!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823770/+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 1823770] [NEW] kernel upgrade changes bios boot order

2019-04-08 Thread Søren Bredlund Caspersen
Public bug reported:

I have a work-laptop which I dual-boot Windows and Ubuntu.

I need Windows for work, and have that as the default boot option in the bios.
But after an upgrade of the Ubuntu Linux kernel Ubuntu gets moved to the top of 
the bios boot-order, and Windows gets moved down.

It doesn't take long to change back, but is a inconvenience. 
It is a T480s ThinkPad with SecureBoot enabled.

It has happened before, but I haven't gotten around to reporting it. It
happened lately with

cat /proc/version_signature 
Ubuntu 4.15.0-47.50-generic 4.15.18

Let me know if you need any other info, and I shall do my best to get it
to you.

Cheers, and thanks for your good work!

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


** Tags: bios boot

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1823770/+attachment/5254221/+files/lspci-vnvn.log

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

Title:
  kernel upgrade changes bios boot order

Status in linux package in Ubuntu:
  New

Bug description:
  I have a work-laptop which I dual-boot Windows and Ubuntu.

  I need Windows for work, and have that as the default boot option in the bios.
  But after an upgrade of the Ubuntu Linux kernel Ubuntu gets moved to the top 
of the bios boot-order, and Windows gets moved down.

  It doesn't take long to change back, but is a inconvenience. 
  It is a T480s ThinkPad with SecureBoot enabled.

  It has happened before, but I haven't gotten around to reporting it.
  It happened lately with

  cat /proc/version_signature 
  Ubuntu 4.15.0-47.50-generic 4.15.18

  Let me know if you need any other info, and I shall do my best to get
  it to you.

  Cheers, and thanks for your good work!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823770/+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 1815691] Missing required logs.

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

apport-collect 1815691

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

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

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

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

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

Title:
  disk not detected on an Intel NUC7i5BNHXF

Status in linux package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Incomplete
Status in ubiquity source package in Disco:
  Invalid

Bug description:
  I attempted to install Ubuntu from multiple ISOs, made with dd to a
  USB disk, onto an Intel NUC7i5BNHXF and none of them were able to
  detect the disk on the system. I was able to successfully install
  Ubuntu 16.04! using the image identified linked to from here:

  https://www.ubuntu.com/download/iot/intel-nuc-desktop

  Attached you will find the syslog files from the the different live
  environments from which I was unable to install Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815691/+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 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-08 Thread Kai-Heng Feng
It should be 4.18.0-18-generic.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session wayland-session
  Uname: Linux 4.18.0-15-generic 

[Kernel-packages] [Bug 1815691] Re: disk not detected on an Intel NUC7i5BNHXF

2019-04-08 Thread Mathieu Trudel-Lapierre
Given the options shown in firmware and switching to AHCI fixes things
as per xnox's comments; this is squarely a "kernel" issue -- one we
can't really fix in ubiquity in any case.

The kernel side, to support this new RAID or "Intel RST" mode comes with
its own set of problems, but I'll let the kernel team deal with that.
It's complicated.

Reassigning to linux.

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

** Changed in: ubiquity (Ubuntu Disco)
   Status: Triaged => Invalid

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

Title:
  disk not detected on an Intel NUC7i5BNHXF

Status in linux package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Incomplete
Status in ubiquity source package in Disco:
  Invalid

Bug description:
  I attempted to install Ubuntu from multiple ISOs, made with dd to a
  USB disk, onto an Intel NUC7i5BNHXF and none of them were able to
  detect the disk on the system. I was able to successfully install
  Ubuntu 16.04! using the image identified linked to from here:

  https://www.ubuntu.com/download/iot/intel-nuc-desktop

  Attached you will find the syslog files from the the different live
  environments from which I was unable to install Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815691/+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 1823547] Re: Kernel crash during boot with IOMMU - on Dual GPU AMD system using Ryzen 7 1700

2019-04-08 Thread Kai-Heng Feng
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.1-rc3 kernel [0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed”, and attach dmesg.

Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc3/

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

Title:
  Kernel crash during boot with IOMMU - on Dual GPU AMD system using
  Ryzen 7 1700

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have this issue with a Ryzen 7 1700 with the following setups:

  Setup 1:
  Motherboard: Gigabyte B450 Aorus M (Latest BIOS installed)
  RAM: 32 GB DDR4 Crucial 3000 Mhz
  GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5
  GPU2: Asus Mining Radeon RX 470 4G GDDR5
  SSD: 240 GB WD Green

  Setup 2:
  Motherboard: ASRock AB350M Pro4 (Latest BIOS installed)
  RAM: 32 GB DDR4 Crucial 3000 Mhz
  GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5
  GPU2: Sapphire Radeon RX 550 2G GDDR5
  SSD: 240 GB WD Green

  The issue first started after installing the second GPU on each of the
  systems. I can't even boot the system, as the errors appear right
  after BIOS initialization.

  The errors are like:

  [exerpt]
  AMD-Vi: Completion-Wait loop timed out
  AMD-Vi: Completion-Wait loop timed out
  AMD-Vi: Completion-Wait loop timed out

  ...

  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0
  address=0x000174bb7560]

  Entering emergecy mode. Exit the shell to continue.
  Type "journalctl" to view system logs.

  

  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 
address=0x000174bb75d0]
  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 
address=0x000174bb7700]
  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 
address=0x000174bb7630]
  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 
address=0x000174bb7660]
  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 
address=0x000174bb7690]
  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 
address=0x000174bb76c0]
  AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 
address=0x000174bb76f0]

  ...

  AMD-Vi: Completion-Wait loop timed out
  AMD-Vi: Event logged [IO_PAGE_FAULT device=23:00.3 domain=0x000 
address=0xfffd3990 flags=0x0070]

  ...

  Buffer I/O error on dev dm-0, logical block 104857472, async page read
  Buffer I/O error on dev dm-0, logical block 104857473, async page read
  Buffer I/O error on dev dm-0, logical block 104857474, async page read
  Buffer I/O error on dev dm-0, logical block 104857475, async page read
  Buffer I/O error on dev dm-0, logical block 104857476, async page read
  Buffer I/O error on dev dm-0, logical block 104857477, async page read

  .

  I can't even install any new system, because the errors are the
  same...

  After some research I discovered that it is a IOMMU issue.
  I turned IOMMU off on both motherboards, and I managed to boot the system.

  I have been trying with CentOS 7, Ubuntu 18.04.2 and Fedora 29.

  I am an architect and I use blender for GPU rendering (this is the
  idea of having two cards), but the AMDGPU-Pro driver from the AMD's
  website (the only one that Blender uses for GPU rendering, as it can't
  use the open one) affects the way Gnome works on Xorg. In Ubuntu 18.04
  Gnome doesn't start at all, it hangs up stating an error about snapd.
  Even after purging snapd, it still doesn't start... Fedora 29 is the
  only one that works, but the official AMDGPU-Pro don't work in it,
  thus I don't have the GPU rendering available.

  Any ideas? Two years have passed, or probably even more, and this
  IOMMU issues on AMD are yet not resolved... I have two different
  chipsets on my MBs (B350 and B450) and the issues are still there...

  Please help. Last resort is to start using Windows, after 15 years of
  using only Linux, but I don't really find this very appealing...

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823547/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2019-04-08 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

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

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1747463/+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 1747463]

2019-04-08 Thread nickel
(In reply to Nikolai from comment #17)
> Hi,
>   I still encounter a same issue concerned to ext4 fs corruption using linux
> kernels 4.19.16... 4.20.27 on HP laptop 17-ak041ur (2 pcs on hand).
> 
>   Laptop configs are A6-9220 radeon r4 5 compute cores 2c+3g, 4G RAM, 200GB
> Intel SSD (1st laptop) or 500GB Toshiba HDD (2nd laptop)

This patch works for me:

https://lkml.org/lkml/2019/4/8/331

One also can use a 'pci=noats' as a temporary countermeasure.

Thanks to Joerg Roedel  who guided me to a solution.

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1690085]

2019-04-08 Thread dyson8
I used the rifw=alfie with a 1700x on an MSI X370 Gaming Plus BIOS
7A33v5H with no freezing for 1 week.  Computer was rock solid on older
BIOS (7A33v55) for a year+ until BIOS update to latest.


I'm using low power idle option with kernel 4.14.111 opensuse 15.0.


PC had kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) 
- After BIOS update and gone now after patch in Comment 580 with rifw=alfie 
boot option.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  

[Kernel-packages] [Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Invalid

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822807 (xenial/linux-gcp)
  
  -- swm properties --
  kernel-stable-master-bug: 1822820
- phase: Ready for Packaging
- phase-changed: Wednesday, 03. April 2019 09:04 UTC
+ phase: Packaging
+ phase-changed: Monday, 08. April 2019 16:07 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-gcp: 4.15.0-1030.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Packaging
  phase-changed: Monday, 08. April 2019 16:07 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822808/+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 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1822820
- phase: Promote to Proposed
- phase-changed: Monday, 08. April 2019 09:57 UTC
+ phase: Testing
+ phase-changed: Monday, 08. April 2019 15:06 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 15:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+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 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:18/beta'
-   snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:18/edge'
+   snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
+ amd64:18/candidate'
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1036.38 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
  amd64:18/candidate'
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2019-04-08 Thread Another User
Aroiu Ovidiu, had you posted "this topic" problem on acer community site? Or 
you have another issue?
Also this problem listed on AMD community. And question even marked as answered.
https://community.amd.com/thread/234045

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

2019-04-08 Thread Stefan Bader
** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1030.32 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux-gcp: 4.15.0-1030.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822807 (xenial/linux-gcp)

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Packaging
  phase-changed: Monday, 08. April 2019 16:07 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822808/+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 1823753] Missing required logs.

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

apport-collect 1823753

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

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

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

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

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1823754] Re: Set CONFIG_RANDOM_TRUST_CPU=y

2019-04-08 Thread Seth Forshee
** Changed in: linux-aws (Ubuntu)
   Importance: Undecided => High

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

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

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

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

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

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

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

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

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

Title:
  Set CONFIG_RANDOM_TRUST_CPU=y

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: Turning this option on will make our kernels by default trust
  the CPU's random number generator for the purpose of initializing the
  kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at
  boot time by passing random.trust_cpu=off. Turning this on has the
  potential to prevent getrandom(2) from blocking during early boot.
  This option was turned on in the master kernel shortly before disco
  kernel freeze; this bug is about propagating the option to derivative
  kernels.

  Regression Potential: No user-visible regressions are expected. Some
  security-conscious users may prefer to not trust the CPU maker's RNG,
  but in that case the boot options is available.

  Test Case: The benefit is difficult to verify empirically in Ubuntu
  kernels since we carry a patch to avoid problems with getrandom(2)
  blocking immediately following boot. However, it is possible to see
  whether or not the kernel used the CPU RNG for initializing the CRNG
  by searching for the string "random: crng done (trusting CPU's
  manufacturer)" in dmesg.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823754/+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 1823753] [NEW] arm64: cma_alloc errors at boot

2019-04-08 Thread dann frazier
Public bug reported:

On some arm64 systems[*] we are seeing a spew of messages on the
console:

[   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

This appears to be non-fatal - impacted systems all eventually boot.
But, at least in the case of the HP m400, it slows down boot enough that
MAAS' default timeout will expire before completing deployment.

[*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as
an HP m400 (APM X-Gene) cartridge - although, not on another one that -
in theory - should be identical.

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

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1711407] Re: unregister_netdevice: waiting for lo to become free

2019-04-08 Thread Dan Streetman
** Changed in: linux (Ubuntu Trusty)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  unregister_netdevice: waiting for lo to become free

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

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+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 1822820] Re: linux: 4.15.0-48.51 -proposed tracker

2019-04-08 Thread Stefan Bader
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
- derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 
1822981 (linux), bug 1823254 (linux)
+ derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 
1822981 (linux), bug 1823254 (linux), bug 1823755 (linux-gke)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.15.0-48.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 
(linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 
(linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 
1822981 (linux), bug 1823254 (linux), bug 1823755 (linux-gke)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+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 1823754] [NEW] Set CONFIG_RANDOM_TRUST_CPU=y

2019-04-08 Thread Seth Forshee
Public bug reported:

SRU Justification

Impact: Turning this option on will make our kernels by default trust
the CPU's random number generator for the purpose of initializing the
kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at
boot time by passing random.trust_cpu=off. Turning this on has the
potential to prevent getrandom(2) from blocking during early boot. This
option was turned on in the master kernel shortly before disco kernel
freeze; this bug is about propagating the option to derivative kernels.

Regression Potential: No user-visible regressions are expected. Some
security-conscious users may prefer to not trust the CPU maker's RNG,
but in that case the boot options is available.

Test Case: The benefit is difficult to verify empirically in Ubuntu
kernels since we carry a patch to avoid problems with getrandom(2)
blocking immediately following boot. However, it is possible to see
whether or not the kernel used the CPU RNG for initializing the CRNG by
searching for the string "random: crng done (trusting CPU's
manufacturer)" in dmesg.

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

** Affects: linux-azure (Ubuntu)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

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

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

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

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

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

Title:
  Set CONFIG_RANDOM_TRUST_CPU=y

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact: Turning this option on will make our kernels by default trust
  the CPU's random number generator for the purpose of initializing the
  kernel's CRNG on Intel, AMD, and IBM CPUs. Users can disable this at
  boot time by passing random.trust_cpu=off. Turning this on has the
  potential to prevent getrandom(2) from blocking during early boot.
  This option was turned on in the master kernel shortly before disco
  kernel freeze; this bug is about propagating the option to derivative
  kernels.

  Regression Potential: No user-visible regressions are expected. Some
  security-conscious users may prefer to not trust the CPU maker's RNG,
  but in that case the boot options is available.

  Test Case: The benefit is difficult to verify empirically in Ubuntu
  kernels since we carry a patch to avoid problems with getrandom(2)
  blocking immediately following boot. However, it is possible to see
  whether or not the kernel used the CPU RNG for initializing the CRNG
  by searching for the string "random: crng done (trusting CPU's
  manufacturer)" in dmesg.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823754/+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 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected 
channel(s):
- amd64:18/candidate'
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1036.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+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 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

2019-04-08 Thread Stefan Bader
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
- derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 
(linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 
1822830 (linux-fips)
+ derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.4.0-146.172 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 
(linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 04. April 2019 18:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+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 1741564] Re: buggy TSC_DEADLINE not disabled for xenial/trusty kernels

2019-04-08 Thread Dan Streetman
** Changed in: linux (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Trusty)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

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

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

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

Title:
  buggy TSC_DEADLINE not disabled for xenial/trusty kernels

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New

Bug description:
  [Impact]
  An upstream commit added Intel cpu model/microcode checks to disable 
TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date: Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  That commit is included in the Ubuntu kernels starting at artful
  v4.13.

  
  The Xenial 4.4 and Trusty 3.13 kernels do not yet have this commit, and so 
may trigger the TSC_DEADLINE microcode bug.  

  Some details on the errata, under HSD173 (page 66):
  
https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/4th-gen-core-family-desktop-specification-update.pdf

  The kernel commit initially working around this microcode errata
  contains a description of what happens when the bug is triggered, "TSC
  deadline timer stops working or creates an interrupt storm..." (from
  commit 855615eee9b1989cac8ec5eaae4562db081a239b which removes the
  workaround after adding microcode level check).

  [Test Case]

  On a system with a CPU model and microcode containing the TSC errata,
  check the /proc/cpuinfo contents; if the 'tsc_deadline_timer' feature
  is listed, this bug exists.  After patching, it should not be listed
  as a CPU feature.  The specific model/stepping/ucode numbers are
  listed in the commits (bd9240a18edfbfa72e957fc2ba831cf1f13ea073 and
  616dd5872e52493863b0202632703eebd51243dc).

  [Regression Potential]

  The major regression potentials I see for this are:

  1) incorrectly disabling the TSC_DEADLINE timer, on a system where the 
microcode errata doesn't apply, and
  2) new reports of problems by T and X users who previously did not know their 
CPU microcode was buggy and now see the "TSC_DEADLINE disabled" boot log error, 
and report that as a "new bug".

  [Other Info]

  There are two follow-on fixes/refinements for this that should also be
  backported to T and X kernels:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724612
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724912

  Those commits update the specific microcode levels for specific cpu
  model/steppings, and prevent disabling the timer on virtualized guests
  (where the timer is also virtualized), respectively.

  Additionally several related commits add, and then remove (once the
  microcode-level-checks are in place) workarounds for this microcode
  errata; commits 5bae156241e05d25171b18ee43e49f103c3f8097 and
  8c9b9d87b855226a823b41a77a05f42324497603 (and possibly others) add the
  workaround, then 855615eee9b1989cac8ec5eaae4562db081a239b removes it.
  Those are fist included in 4.10, so neither the T nor X kernels
  include the workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741564/+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 1545330] Re: [wily][regression] systemtap script compilation broken by new kernels

2019-04-08 Thread Dan Streetman
** Changed in: systemtap (Ubuntu Wily)
   Status: Confirmed => Won't Fix

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

Title:
  [wily][regression] systemtap script compilation broken by new kernels

Status in linux package in Ubuntu:
  Fix Released
Status in systemtap package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in systemtap source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in systemtap source package in Xenial:
  Fix Released
Status in systemtap package in Fedora:
  Fix Released

Bug description:
  The following errors appear when compiling any systemtap script:

  In file included from include/linux/mutex.h:15:0,
   from 
/tmp/stapbdpxn3/stap_a0ec17f995e8f89d672d8c2eb7fe7c24_1693_src.c:25:
  include/linux/spinlock_types.h:55:14: error: ‘__ARCH_SPIN_LOCK_UNLOCKED’ 
undeclared here (not in a function)
    .raw_lock = __ARCH_SPIN_LOCK_UNLOCKED, \
    ^
  include/linux/spinlock_types.h:79:15: note: in expansion of macro 
‘__RAW_SPIN_LOCK_INITIALIZER’
    { { .rlock = __RAW_SPIN_LOCK_INITIALIZER(lockname) } }
     ^
  include/linux/spinlock_types.h:82:16: note: in expansion of macro 
‘__SPIN_LOCK_INITIALIZER’
    (spinlock_t ) __SPIN_LOCK_INITIALIZER(lockname)
  ^
  include/linux/mutex.h:111:18: note: in expansion of macro 
‘__SPIN_LOCK_UNLOCKED’
     , .wait_lock = __SPIN_LOCK_UNLOCKED(lockname.wait_lock) \
    ^
  include/linux/mutex.h:117:27: note: in expansion of macro 
‘__MUTEX_INITIALIZER’
    struct mutex mutexname = __MUTEX_INITIALIZER(mutexname)

  Upstream fix:
  
https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=320e1ecb16427b5769f0f5a097d80823ee1fb765

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545330/+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 1811470] Re: [witherspoon] removing module nouveau causes cpu hard lockup

2019-04-08 Thread bugproxy
** Tags removed: targetmilestone-inin18043
** Tags added: targetmilestone-inin---

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

Title:
  [witherspoon] removing module nouveau causes cpu hard lockup

Status in The Ubuntu-power-systems project:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Installed 18.04 and upgraded kernel to linux-image-generic-hwe-18.04
  (4.18.0-13-generic #14~18.04.1-Ubuntu SMP Thu Dec 6 14:03:47). Copied
  gv100 firmware to /lib/firmware/nvidia, removed and reloaded nouveau
  (modprobe -r and modprobe). Tried to remove nouveau again using
  modprobe -r and I see the trace below. After a while the modprobe -r
  command completed the module was removed successfully.

  [  618.185258] nouveau 0035:04:00.0: DRM: failed to idle channel 1 [DRM]
  [  630.314599] watchdog: CPU 4 self-detected hard LOCKUP @ ioread32+0x2c/0x170
  [  630.314601] watchdog: CPU 4 TB:415266697100, last heartbeat 
TB:410146341428 (1ms ago)
  [  630.314601] Modules linked in: nouveau(-) ofpart at24 cmdlinepart 
uio_pdrv_genirq ipmi_powernv ipmi_devintf powernv_flash uio mtd opal_prd 
ipmi_msghandler ibmpowernv vmx_crypto sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm crct10dif_vpmsum ahci crc32c_vpmsum tg3 libahci 
drm_panel_orientation_quirks [last unloaded: nouveau]
  [  630.314629] CPU: 4 PID: 6623 Comm: modprobe Not tainted 4.18.0-13-generic 
#14~18.04.1-Ubuntu
  [  630.314630] NIP:  c0729afc LR: c0080f766990 CTR: 
c0729ad0
  [  630.314630] REGS: c03fffd87d80 TRAP: 0900   Not tainted  
(4.18.0-13-generic)
  [  630.314631] MSR:  9280b033   
CR: 44002824  XER: 
  [  630.314638] CFAR: c0080f7b2ac4 IRQMASK: 1
  [  630.314639] GPR00: c0080f7ad3f8 c03f6c1bb850 c178c200 
c00c8e7e
  [  630.314642] GPR04:    
0008
  [  630.314644] GPR08: c03fa800 7fff c00c8e7e 
c0080f7b2ab0
  [  630.314647] GPR12: c0729ad0 c03fa800 0001 

  [  630.314649] GPR16:   039a7cc60074 
039a7cc3c978
  [  630.314652] GPR20: 039a7cc60070  78448f88 

  [  630.314654] GPR24: 039a8bf40ee8  c0080f82dca0 
c03fed072098
  [  630.314657] GPR28: c000203968a2c290 c000203968840908 c000203968840900 
0001
  [  630.314660] NIP [c0729afc] ioread32+0x2c/0x170
  [  630.314660] LR [c0080f766990] nouveau_bo_rd32+0x48/0x70 [nouveau]
  [  630.314661] Call Trace:
  [  630.314662] [c03f6c1bb850] [c03f6c1bb890] 0xc03f6c1bb890 
(unreliable)
  [  630.314663] [c03f6c1bb880] [c03f6c1bb8b0] 0xc03f6c1bb8b0
  [  630.314664] [c03f6c1bb8a0] [c0080f7ad3f8] 
nv84_fence_read+0x40/0x60 [nouveau]
  [  630.314666] [c03f6c1bb8c0] [c0080f7aab3c] 
nouveau_fence_update+0x44/0x100 [nouveau]
  [  630.314667] [c03f6c1bb900] [c0080f7ab5d8] 
nouveau_fence_done+0x100/0x180 [nouveau]
  [  630.314668] [c03f6c1bb940] [c0080f7ab8c8] 
nouveau_fence_wait+0x90/0x150 [nouveau]
  [  630.314669] [c03f6c1bb970] [c0080f7a8f90] 
nouveau_channel_idle+0xd8/0x140 [nouveau]
  [  630.314670] [c03f6c1bba00] [c0080f75f75c] 
nouveau_accel_fini+0x74/0xe0 [nouveau]
  [  630.314671] [c03f6c1bba30] [c0080f75f8e8] 
nouveau_drm_unload+0x60/0x130 [nouveau]
  [  630.314672] [c03f6c1bba60] [c00813b1b118] 
drm_dev_unregister+0x70/0x160 [drm]
  [  630.314673] [c03f6c1bbaa0] [c00813b1b3f0] drm_put_dev+0x48/0xa0 
[drm]
  [  630.314675] [c03f6c1bbb10] [c0080f760f8c] 
nouveau_drm_device_remove+0x54/0x90 [nouveau]
  [  630.314676] [c03f6c1bbb50] [c07a746c] 
pci_device_remove+0x6c/0x120
  [  630.314677] [c03f6c1bbb90] [c08a7014] 
device_release_driver_internal+0x294/0x380
  [  630.314678] [c03f6c1bbbe0] [c08a719c] driver_detach+0x7c/0x140
  [  630.314679] [c03f6c1bbc20] [c08a5304] 
bus_remove_driver+0x84/0x170
  [  630.314680] [c03f6c1bbc90] [c08a7ef8] 
driver_unregister+0x48/0x90
  [  630.314681] [c03f6c1bbd00] [c07a52b8] 
pci_unregister_driver+0x38/0x150
  [  630.314682] [c03f6c1bbd50] [c0080f7af048] 
nouveau_drm_exit+0x30/0xfc08 [nouveau]
  [  630.314683] [c03f6c1bbd70] [c01e6b14] 
sys_delete_module+0x1d4/0x310
  [  630.314684] [c03f6c1bbe30] [c000b288] system_call+0x5c/0x70
  [  630.314685] Instruction dump:
  [  630.314686] 

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

2019-04-08 Thread bugproxy
--- Comment From leona...@ibm.com 2019-04-08 10:37 EDT---
This (In reply to comment #64)
> Hi Leonardo,
> unfortunately there was an issue with the SRU request and Juerg NACK-ed it,
> please have a look here:
> https://lists.ubuntu.com/archives/kernel-team/2019-March/099128.html
> Please re-submit the SRU request with the requested corrections.

The email you posted was from March 10, and is outdated. The changes
required were made, and it was acked on March 13, as said on the
previous comment.

Please see https://lists.ubuntu.com/archives/kernel-
team/2019-March/099221.html

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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 1811470] Re: [witherspoon] removing module nouveau causes cpu hard lockup

2019-04-08 Thread Manoj Iyer
** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: ubuntu-power-systems
   Status: Triaged => Won't Fix

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

Title:
  [witherspoon] removing module nouveau causes cpu hard lockup

Status in The Ubuntu-power-systems project:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Installed 18.04 and upgraded kernel to linux-image-generic-hwe-18.04
  (4.18.0-13-generic #14~18.04.1-Ubuntu SMP Thu Dec 6 14:03:47). Copied
  gv100 firmware to /lib/firmware/nvidia, removed and reloaded nouveau
  (modprobe -r and modprobe). Tried to remove nouveau again using
  modprobe -r and I see the trace below. After a while the modprobe -r
  command completed the module was removed successfully.

  [  618.185258] nouveau 0035:04:00.0: DRM: failed to idle channel 1 [DRM]
  [  630.314599] watchdog: CPU 4 self-detected hard LOCKUP @ ioread32+0x2c/0x170
  [  630.314601] watchdog: CPU 4 TB:415266697100, last heartbeat 
TB:410146341428 (1ms ago)
  [  630.314601] Modules linked in: nouveau(-) ofpart at24 cmdlinepart 
uio_pdrv_genirq ipmi_powernv ipmi_devintf powernv_flash uio mtd opal_prd 
ipmi_msghandler ibmpowernv vmx_crypto sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm crct10dif_vpmsum ahci crc32c_vpmsum tg3 libahci 
drm_panel_orientation_quirks [last unloaded: nouveau]
  [  630.314629] CPU: 4 PID: 6623 Comm: modprobe Not tainted 4.18.0-13-generic 
#14~18.04.1-Ubuntu
  [  630.314630] NIP:  c0729afc LR: c0080f766990 CTR: 
c0729ad0
  [  630.314630] REGS: c03fffd87d80 TRAP: 0900   Not tainted  
(4.18.0-13-generic)
  [  630.314631] MSR:  9280b033   
CR: 44002824  XER: 
  [  630.314638] CFAR: c0080f7b2ac4 IRQMASK: 1
  [  630.314639] GPR00: c0080f7ad3f8 c03f6c1bb850 c178c200 
c00c8e7e
  [  630.314642] GPR04:    
0008
  [  630.314644] GPR08: c03fa800 7fff c00c8e7e 
c0080f7b2ab0
  [  630.314647] GPR12: c0729ad0 c03fa800 0001 

  [  630.314649] GPR16:   039a7cc60074 
039a7cc3c978
  [  630.314652] GPR20: 039a7cc60070  78448f88 

  [  630.314654] GPR24: 039a8bf40ee8  c0080f82dca0 
c03fed072098
  [  630.314657] GPR28: c000203968a2c290 c000203968840908 c000203968840900 
0001
  [  630.314660] NIP [c0729afc] ioread32+0x2c/0x170
  [  630.314660] LR [c0080f766990] nouveau_bo_rd32+0x48/0x70 [nouveau]
  [  630.314661] Call Trace:
  [  630.314662] [c03f6c1bb850] [c03f6c1bb890] 0xc03f6c1bb890 
(unreliable)
  [  630.314663] [c03f6c1bb880] [c03f6c1bb8b0] 0xc03f6c1bb8b0
  [  630.314664] [c03f6c1bb8a0] [c0080f7ad3f8] 
nv84_fence_read+0x40/0x60 [nouveau]
  [  630.314666] [c03f6c1bb8c0] [c0080f7aab3c] 
nouveau_fence_update+0x44/0x100 [nouveau]
  [  630.314667] [c03f6c1bb900] [c0080f7ab5d8] 
nouveau_fence_done+0x100/0x180 [nouveau]
  [  630.314668] [c03f6c1bb940] [c0080f7ab8c8] 
nouveau_fence_wait+0x90/0x150 [nouveau]
  [  630.314669] [c03f6c1bb970] [c0080f7a8f90] 
nouveau_channel_idle+0xd8/0x140 [nouveau]
  [  630.314670] [c03f6c1bba00] [c0080f75f75c] 
nouveau_accel_fini+0x74/0xe0 [nouveau]
  [  630.314671] [c03f6c1bba30] [c0080f75f8e8] 
nouveau_drm_unload+0x60/0x130 [nouveau]
  [  630.314672] [c03f6c1bba60] [c00813b1b118] 
drm_dev_unregister+0x70/0x160 [drm]
  [  630.314673] [c03f6c1bbaa0] [c00813b1b3f0] drm_put_dev+0x48/0xa0 
[drm]
  [  630.314675] [c03f6c1bbb10] [c0080f760f8c] 
nouveau_drm_device_remove+0x54/0x90 [nouveau]
  [  630.314676] [c03f6c1bbb50] [c07a746c] 
pci_device_remove+0x6c/0x120
  [  630.314677] [c03f6c1bbb90] [c08a7014] 
device_release_driver_internal+0x294/0x380
  [  630.314678] [c03f6c1bbbe0] [c08a719c] driver_detach+0x7c/0x140
  [  630.314679] [c03f6c1bbc20] [c08a5304] 
bus_remove_driver+0x84/0x170
  [  630.314680] [c03f6c1bbc90] [c08a7ef8] 
driver_unregister+0x48/0x90
  [  630.314681] [c03f6c1bbd00] [c07a52b8] 
pci_unregister_driver+0x38/0x150
  [  630.314682] [c03f6c1bbd50] [c0080f7af048] 
nouveau_drm_exit+0x30/0xfc08 [nouveau]
  [  630.314683] [c03f6c1bbd70] [c01e6b14] 
sys_delete_module+0x1d4/0x310
  [  630.314684] [c03f6c1bbe30] [c000b288] 

[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10

2019-04-08 Thread Manoj Iyer
** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: ubuntu-power-systems
   Status: Confirmed => Incomplete

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

Title:
  CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg
  error Checking for all LINUX clients for devops4p10

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

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2018-04-20 05:56:03 ==

  
  == Comment: #1 - Application Cdeadmin  - 2018-04-20 
05:56:05 ==
   State: Open by: stccdenv on 18 April 2018 06:27:28 

  This defect was opened automatically using defect_template with only
  logs. Please refer to 2nd seq for the problem description.

  ==Automatic entries==
  Full Log: 
http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138

  Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy 
Adams(tnad...@us.ibm.com)
  Backup: Atit Patel (a...@us.ibm.com)

  System Name: devops4fp1
  FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com)
  System Firmware Level:
   Current Side Driver:.fips861/b0413a_1816.861
   Non-Current Side Driver:.fips861/b0410a_1816.861

  Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab 
password. (The Lab Test Passwords are now accessible only through the auto or 
manual install web apps. For example, from the manual install web app, enter 
your email address, check the Lab Passwords checkbox and then click on Submit.)
  (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then 
ssh/telnet to 10.33.x.x lpars)

  ---
  HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com)
  HMC Version:
  "version= Version: 9
   Release: 1
   Service Pack: 910
  HMC Build level 1803052221
  ","base_version=V9R1
  "

  ---

  =Logs
  SNAP : 
  devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149  
/tmp/IBM.DRM.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02  
/tmp/htx.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02  
  devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149  
/tmp/IBM.DRM.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03  
/tmp/htx.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03  
  devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148  
/tmp/IBM.DRM.180418060148.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04  
/tmp/htx.180418060148.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04  
  devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148  
/tmp/IBM.DRM.180418060148.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05  
/tmp/htx.180418060148.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05  
  devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz  
/tmp/var_log.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz  
/var/log/nts_linux-hjmh_180418_0703.tbz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/nts_linux-hjmh_180418_0703.tbz  
/tmp/IBM.DRM.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p06  
/tmp/htx.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p06  
  devops4p07: /tmp/ctsupt/ctsnap.devops4p07.04180601.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.devops4p07.04180601.tar.gz  
/tmp/var_log.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz  
/var/tmp/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.xz and 
also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.xz
  /tmp/IBM.DRM.180418060149.tar.gz and also @ 
(NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p07  

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-04-08 Thread Frank Heimes
Hi Leonardo,
unfortunately there was an issue with the SRU request and Juerg NACK-ed it, 
please have a look here:
https://lists.ubuntu.com/archives/kernel-team/2019-March/099128.html
Please re-submit the SRU request with the requested corrections.

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-04-08 Thread Manoj Iyer
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Incomplete

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

** Changed in: ubuntu-power-systems
   Status: In Progress => Incomplete

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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


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

2019-04-08 Thread Manoj Iyer
The fixes identified here are available in Bionic:
5be6b75610ce cfq-iosched: fix the delay of cfq_group's vdisktime under iops mode
142bbdfccc8b cfq: Disable writeback throttling by default

marking this bug as fix-released. Please retest with latest Bionic
kernel and reopen this bug if this is still an issue.

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

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

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

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

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released

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

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

  ---uname output---
  4.10.0-11-generic - still valid up to latest kernel in Bionic

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

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

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

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

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

  Tests are running again, will see what happens next.

  Update from JIRA:

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

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

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

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

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

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

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

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may 

[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
- phase: Promote to Proposed
- phase-changed: Monday, 08. April 2019 10:36 UTC
+ phase: Testing
+ phase-changed: Monday, 08. April 2019 14:06 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:18/beta'
+   snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:18/edge'
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws: 4.15.0-1036.38 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Monday, 08. April 2019 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:18/beta'
snap-release-to-edge: 'Pending -- snap aws-kernel not in expected 
channel(s): amd64:18/edge'
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+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 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-04-08 Thread Manoj Iyer
** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+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 1822882] Re: linux-lts-trusty: -proposed tracker

2019-04-08 Thread Stefan Bader
** Tags removed: kernel-sru-backport-of-1822883

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- kernel-stable-master-bug: 1822883
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 14:32 UTC
  reason:
prepare-package: Pending -- version not specified

** Tags removed: kernel-release-tracking-bug-live

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Invalid

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

Title:
  linux-lts-trusty:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 14:32 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822882/+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 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1822820
  phase: Promote to Proposed
  phase-changed: Monday, 08. April 2019 09:57 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1822820
  phase: Promote to Proposed
  phase-changed: Monday, 08. April 2019 09:57 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+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 1822883] Re: linux: 3.13.0-169.219 -proposed tracker

2019-04-08 Thread Stefan Bader
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
- 
- backports: bug 1822882 (precise/linux-lts-trusty)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 05. April 2019 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 3.13.0-169.219 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 05. April 2019 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822883/+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 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-04-08 Thread Daniel Axtens
Hi Michael R,

I tried to apply your patches to test them and support the effort to get
them included in the Bionic kernel, but I'm having some trouble applying
them:

ubuntu@dja-bionic:~/bionic$ git am 
../patches/01-powerpc-64s-add-support-for-ori-barrier_nospec.patch
Patch format detection failed.
ubuntu@dja-bionic:~/bionic$ git am 
../patches/01-powerpc-64s-add-support-for-ori-barrier_nospec.patch 
--patch-format mbox
Applying: commit 2eea7f067f495e33b8b116b35b5988ab2b8aec55
fatal: empty ident name (for <>) not allowed

How are you generating them? They don't look like they've been generated
with git format-patch...?

Regards,
Daniel

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

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

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

Bug description:
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+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 1823725] Missing required logs.

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

apport-collect 1823725

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

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

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

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

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

Title:
  packet: reset network header if packet shorter than ll reserved space

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After backport of linux upstream commit 9ed988cd5915 ("packet:
  validate variable length ll headers")
  (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
  missing :

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

  9ed988cd5915 ("packet: validate variable length ll headers")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823725/+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 1823725] [NEW] packet: reset network header if packet shorter than ll reserved space

2019-04-08 Thread Nicolas Dichtel
Public bug reported:

After backport of linux upstream commit 9ed988cd5915 ("packet: validate
variable length ll headers") (https://kernel.ubuntu.com/git/ubuntu
/ubuntu-bionic.git/commit/?id=c6026847a0a1) the following upstream patch
is missing :

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

9ed988cd5915 ("packet: validate variable length ll headers")

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

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

Title:
  packet: reset network header if packet shorter than ll reserved space

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After backport of linux upstream commit 9ed988cd5915 ("packet:
  validate variable length ll headers")
  (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
  bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
  missing :

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

  9ed988cd5915 ("packet: validate variable length ll headers")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823725/+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 1819924] Re: System hangs when hot-plugging dual monitor dock

2019-04-08 Thread Bernie Bernstein
Issue still remains with the mainline kernel.  The contents of the
kernel Oops message differs slightly, but still very similar:

[   27.532858] BUG: unable to handle kernel NULL pointer dereference at 
03e8
[   27.532862] #PF error: [WRITE]
[   27.532865] PGD 0 P4D 0
[   27.532869] Oops: 0002 [#1] SMP NOPTI
[   27.532873] CPU: 3 PID: 82 Comm: kworker/3:1 Not tainted 
5.1.0-050100rc3-generic #201904010618
[   27.532875] Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 
01.04.01 09/13/2018
[   27.532982] Workqueue: events dm_irq_work_func [amdgpu]
[   27.532989] RIP: 0010:queue_work_on+0x1b/0x40
[   27.532992] Code: 75 01 01 e8 f9 13 fe ff 0f 0b e9 b5 fc ff ff 0f 1f 44 00 
00 55 48 89 e5 53 9c 58 0f 1f 44 00 00 48 89 c3 fa 66 0f 1f 44 00 00  48 0f 
ba 2a 00 73 11 31 c9 48 89 df 57 9d 0f 1f 44 00 00 89 c8
[   27.532994] RSP: 0018:c16bc1eebc88 EFLAGS: 00010002
[   27.532996] RAX: 0202 RBX: 0202 RCX: 0001
[   27.532998] RDX: 03e8 RSI: 9dde1e80d200 RDI: 2000
[   27.533000] RBP: c16bc1eebc90 R08: 00027080 R09: b8210b0b
[   27.533002] R10: fc35106d5500 R11: 9dde1e86ca90 R12: 9dde0f2db646
[   27.533003] R13: 9dde1b4b9a80 R14: 9dde195eb000 R15: 
[   27.533006] FS:  () GS:9dde1ecc() 
knlGS:
[   27.533008] CS:  0010 DS:  ES:  CR0: 80050033
[   27.533010] CR2: 03e8 CR3: 000411ca6000 CR4: 003406a0
[   27.533011] Call Trace:
[   27.533026]  drm_dp_mst_handle_up_req+0x503/0x550 [drm_kms_helper]
[   27.533037]  drm_dp_mst_hpd_irq+0xbe/0xaa0 [drm_kms_helper]
[   27.533045]  ? drm_dp_mst_hpd_irq+0xbe/0xaa0 [drm_kms_helper]
[   27.533133]  handle_hpd_rx_irq+0x22c/0x2e0 [amdgpu]
[   27.533219]  ? handle_hpd_rx_irq+0x22c/0x2e0 [amdgpu]
[   27.533306]  dm_irq_work_func+0x53/0x70 [amdgpu]
[   27.533309]  process_one_work+0x20f/0x410
[   27.533312]  worker_thread+0x34/0x400
[   27.533315]  kthread+0x120/0x140
[   27.533318]  ? process_one_work+0x410/0x410
[   27.533320]  ? __kthread_parkme+0x70/0x70
[   27.533325]  ret_from_fork+0x22/0x40
[   27.533327] Modules linked in: cmac bnep btusb btrtl btbcm btintel bluetooth 
ecdh_generic bonding uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_common videodev media nfc edac_mce_amd kvm_amd ccp kvm arc4 irqbypass 
nls_iso8859_1 crct10dif_pclmul crc32_pclmul snd_hda_codec_conexant 
ghash_clmulni_intel snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel iwlmvm 
snd_seq_midi snd_seq_midi_event aes_x86_64 crypto_simd mac80211 cryptd 
snd_rawmidi glue_helper snd_seq iwlwifi snd_seq_device joydev snd_timer 
input_leds hp_wmi serio_raw sparse_keymap wmi_bmof snd k10temp cfg80211 
soundcore ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec hp_wireless 
mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 
amdgpu chash gpu_sched amd_iommu_v2 i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops nvme psmouse ahci drm libahci i2c_piix4 r8169 
nvme_core realtek
[   27.533372]  wmi i2c_hid hid video
[   27.533378] CR2: 03e8
[   27.533380] ---[ end trace af80d2e3030b9f18 ]---


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

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

Title:
  System hangs when hot-plugging dual monitor dock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking
  Station into my system, after it has already booted, the system hangs
  with a kernel OOPS.  This is always repeatable.

  Steps to reproduce:

  1. Ensure docking station is unplugged or shut-off.
  2. Boot up computer.
  3. Turn-on docking station and plug into to system.

  If the docking station is plugged in before the system boots, it works
  fine.  It can even be unpluged and hot-plugged without issue at that
  point.

  This kernel Oops occurs when the system hangs:

  BUG: unable to handle kernel NULL pointer dereference at 0320
  PGD 0 P4D 0
  SMP NOPTI
  CPU: 3 PID: 84 Comm: kworker/3:1 Tainted: G  DOE 
4.18.0-16-generic #17-Ubuntu  
  Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018
  Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper]
  RIP: 0010:mutex_lock+0x1d/0x30 
  Code: 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 
89 fb e8 8e df ff ff 31 c0 65 48 8b 14 25 00 5c 01 00  48 0f b1 13 74 08 48 
89 df e8 b4 ff ff ff 5b 5d c3 90 0f 1f 44
  RSP: 0018:b6c0c1efbd78 EFLAGS: 00010246
  RAX:  RBX: 0320 RCX: 8ed7cfb5c800
  RDX: 8ed7d383 RSI: 0202 RDI: 0320
  RBP: 

[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption

2019-04-08 Thread Jeff Lane
Test kernels are up here:
https://people.canonical.com/~jlane/testkernels/

Please test each and report back

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

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

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

Title:
  amd_iommu possible data corruption

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

Bug description:
  [Impact]
  If a device has an exclusion range specified in the IVRS table, this region 
needs to be reserved in the iova-domain of that device. This hasn't happened 
until now and can cause data corruption on data transfered with these devices.
  
  Treat exclusion ranges as reserved regions in the iommu-core to fix the 
problem.

  This is a clean cherry pick from mainline of
  8aafaaf2212192012f5bae305bb31cdf7681d777

  
  [Test Case]

  
  [Fixes]
  Cherry pick the following from Mainline
  fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range 
in iova-domain

  [Regression Risk]
  Only affects the amd_iommu driver:
  drivers/iommu/amd_iommu*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+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 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1822789 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
- amd64:18/candidate'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1822789 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822791
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+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 1820275] Re: btrfs-kernel oops from btrfs subvolume delete command

2019-04-08 Thread Frank Heimes
** Changed in: ubuntu-z-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/1820275

Title:
  btrfs-kernel oops from btrfs subvolume delete command

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  This report show a kernel oops in the btrfs lugin , happened every few
  days when running a test suite on a test system. It looks like their
  systemd/Journal failed to kick off a dump immediately following the
  panic.

  The exploiter is using the kernel 4.15.0-42

  We're not sure it's the btrfs subvolume delete that's causing it yet

  Following infos are attached: - syslog - sosreport - kdump output here
  : https://ibm.ent.box.com/folder/70219521934

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

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


Re: [Kernel-packages] [Bug 1819023] Re: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen

2019-04-08 Thread Jeb E.
Alright, got the computer to reboot a second time and it appears as if the
problem is fixed! The gradient on the login screen isn't a perfect
gradient, but that's a different issue.

Maybe dithering should be forced "off" in a near future update?

On Sun, Apr 7, 2019, 10:00 PM Daniel van Vugt 
wrote:

> That's good news.
>
> Now please try these while the image is open:
>
>   xrandr --output DVI-I-1 --set "dithering mode" "off"
>
> or
>
>   xrandr --output DVI-I-1 --set "dithering mode" "static 2x2"
>
> and change 'DVI-I-1' if you are using a different connector now.
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1819023
>
> Title:
>   [nouveau] Scrolling screen flicker, especially on default Ubuntu lock
>   screen
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   My screen is experiencing a weird "scrolling" flicker, especially
>   while displaying blue, indigo, and violet hues/colors, such as on the
>   default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker
>   scrolls up and down, with the brightest part of the flicker being
>   towards the top, with a gradient that fades back to the original color
>   near the bottom.
>
>   Problem occurs on any one monitor on any one video output protocol
>   (DVI-D, HDMI, and VGA).
>
>
>   I will upload an illustration or render as soon as possible for better
> explanation.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: xorg 1:7.7+19ubuntu8
>   ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
>   Uname: Linux 4.18.0-16-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu13.2
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Mar  7 10:39:50 2019
>   DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to
> execute child process “./xorg_fix_proprietary.py” (No such file or
> directory) (8))
>   DistroCodename: cosmic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if
> 00 [VGA controller])
>  Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
>   InstallationDate: Installed on 2018-08-17 (202 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   MachineType: BIOSTAR Group A880G+
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic
> root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago)
>   dmi.bios.date: 09/21/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 080016
>   dmi.board.asset.tag: To Be Filled By O.E.M.
>   dmi.board.name: A880G+
>   dmi.board.vendor: BIOSTAR Group
>   dmi.chassis.asset.tag: None
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: BIOSTAR Group
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr:
>   dmi.product.family: To Be Filled By O.E.M.
>   dmi.product.name: A880G+
>   dmi.product.sku: To Be Filled By O.E.M.
>   dmi.sys.vendor: BIOSTAR Group
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.95-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819023/+subscriptions
>

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

Title:
  [nouveau] Scrolling screen flicker, especially on default Ubuntu lock
  screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My screen is experiencing a weird "scrolling" flicker, especially
  while displaying blue, indigo, and violet hues/colors, such as on the
  default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker
  scrolls up and down, with the brightest part of the flicker being
  towards the top, with a gradient that fades back to the original color
 

[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822804 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Monday, 08. April 2019 10:36 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux-aws: 4.15.0-1036.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Monday, 08. April 2019 10:36 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+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 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker

2019-04-08 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected 
channel(s):
- amd64:latest/candidate'
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.15.0-1042.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-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 stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822816 (trusty/linux-azure)
  derivatives: bug 1822814 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 05. April 2019 17:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+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 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker

2019-04-08 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-aws: 4.15.0-1036.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1822804 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Monday, 08. April 2019 10:36 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+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


  1   2   >