[Kernel-packages] [Bug 1820832] Re: [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

[Mitchell Clifford]

For AMD users, I finally managed to get my primary display to correctly
update at 144Hz under Xorg by manually enabling TearFree rendering, as
described here:

https://wiki.archlinux.org/index.php/AMDGPU#Tear_Free_Rendering

I manually created the file:
/etc/X11/xorg.conf.d/20-amdgpu.conf

Inside it, I added:

Section "Device"
 Identifier "AMD"
 Driver "amdgpu"
 Option "TearFree" "true"
 Option "VariableRefresh" "true"
EndSection

Then rebooted, and everything was -finally- nice and smooth! :D

Note that I added the "VariableRefresh" option because my monitor
supports FreeSync.  Don't include that line if your monitor doesn't
support variable refresh-rates.

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

Title:
  [nvidia] [xorg] multiple monitors: limits the framerate of faster
  120/144hz monitors to 60hz

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  multiple monitors on xorg
  =

  Was recently discussed over on
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

  Another user + myself have the following issue:

  The slowest connected display limits the FPS. The test case we used is
  over at the top of the other bug report ^^

  This we found today happens with either amd vega graphics, or nvidia
  pascal graphics, the vendor doesn't seem to matter. We have both seen
  the same issue (xorg).

  This is on 18.10, and booting into the 'Gnome (xorg)' login option.
  With the FPS being logged by journalctl -f. With only single monitor
  attached. Then it initially goes as high as the primary monitor can
  show. (And glmark2 running in background, to maintain a continued
  load). Which is 120fps for my case. Then as soon as secondary monitor
  is plugged in, which is a 60hz TV. This is being plugged into the HDMI
  port of the same graphics card in real time. Then the FPS logged by
  'journalctl -f' drops, and becomes capped to 60hz, in the output being
  printed by journalctl -f.

  My setup:
  kernel 5.0.0-05-lowlatency #201903032031
  NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
  ubuntu 18.10

  mutter version:

  mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
  mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all 
[installed]

  To confirm where the '.4' at the very end of the ~ubuntu18.10.4
  version number, it seems to be that we have updated now on our client
  machines the be most recent bugfix updates, kindly provided by Daniel.
  Which closed the other bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
  referred to, as being solved for people's single monitor scenarios.

  Thanks again for the other recent bug fixes in this area, it is a nice
  progress. Very helpful! We hope you can also look into this latest
  problem / issue for the multiple monitor scenario.

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

-- 
Mailing list: https://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

[Matthias Homann]

I installed the proposed kernel and the fix works in principle, but in the 
manual selection the numbering seems swapped. On my HP 250 the antenna cable is 
connected to connector #1 (label printed on the WiFi module) but in the kernel 
module I have to select antenna #2 for a good signal.
Anyhow, this is juts a cosmetic issue for me, thanks for the 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/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 1822793] Re: linux-gcp: 4.18.0-1009.10 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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 1822792 (bionic/linux-gcp-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
- phase: Testing
- phase-changed: Thursday, 04. April 2019 01:05 UTC
+ phase: Signoff
+ phase-changed: Friday, 19. April 2019 07:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1822793

Title:
  linux-gcp: 4.18.0-1009.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  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 1822792 (bionic/linux-gcp-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822796
  phase: Signoff
  phase-changed: Friday, 19. April 2019 07:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1822793/+subscriptions

-- 
Mailing list: https://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 1825488] [NEW] wl driver throws stack trace repeatdly

[zebul666]

Public bug reported:

wl driver is thriwing stack trace repeatdly in log

avril 19 09:13:56 titan kernel: Hardware name: Dell Inc. Inspiron 3521/06RYX8, 
BIOS A12 10/25/2013
avril 19 09:13:56 titan kernel: RIP: 0010:cfg80211_roamed+0x217/0x230 [cfg80211]
avril 19 09:13:56 titan kernel: Code: 00 00 00 49 8d 4d 70 4c 89 f7 45 0f b6 85 
90 00 00 00 6a 02 48 8b 36 e8 37 8c fd ff 48 89 43 08 5a 48 85 c0 0f 8
avril 19 09:13:56 titan kernel: RSP: 0018:ae46c150bdb0 EFLAGS: 00010246
avril 19 09:13:56 titan kernel: RAX:  RBX: ae46c150be00 
RCX: 0002
avril 19 09:13:56 titan kernel: RDX: 0002 RSI: fe01 
RDI: c07b92b4
avril 19 09:13:56 titan kernel: RBP: ae46c150bde0 R08:  
R09: 
avril 19 09:13:56 titan kernel: R10: ae46c150be00 R11: 9c7f769b4fba 
R12: 006000c0
avril 19 09:13:56 titan kernel: R13: 9c7f77550c00 R14: 9c7f769b4300 
R15: dead0100
avril 19 09:13:56 titan kernel: FS:  () 
GS:9c7f870c() knlGS:
avril 19 09:13:56 titan kernel: CS:  0010 DS:  ES:  CR0: 
80050033
avril 19 09:13:56 titan kernel: CR2: 7ffc4c52bbe8 CR3: 000238ada001 
CR4: 001626e0
avril 19 09:13:56 titan kernel: Call Trace:
avril 19 09:13:56 titan kernel:  wl_bss_roaming_done.isra.25+0xd6/0x110 [wl]
avril 19 09:13:56 titan kernel:  ? wl_bss_roaming_done.isra.25+0xd6/0x110 [wl]
avril 19 09:13:56 titan kernel:  wl_notify_roaming_status+0x44/0x60 [wl]
avril 19 09:13:56 titan kernel:  ? down_interruptible+0x33/0x60
avril 19 09:13:56 titan kernel:  wl_event_handler+0x6c/0x150 [wl]
avril 19 09:13:56 titan kernel:  kthread+0x120/0x140
avril 19 09:13:56 titan kernel:  ? wl_notify_scan_status+0x230/0x230 [wl]
avril 19 09:13:56 titan kernel:  ? __kthread_parkme+0x70/0x70
avril 19 09:13:56 titan kernel:  ret_from_fork+0x35/0x40
avril 19 09:13:56 titan kernel: ---[ end trace c5aea32843ce9cab ]---

broadcom-sta-dkms does not behave like that.

But both driver are unable to let me to connect to my AP with AUTH
failed (WPA2 handshake failing)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: bcmwl-kernel-source (not installed)
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 10:47:04 2019
InstallationDate: Installed on 2018-05-07 (346 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: bcmwl
UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)

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


** Tags: amd64 apport-bug disco wayland-session

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

Title:
  wl driver throws stack trace repeatdly

Status in bcmwl package in Ubuntu:
  New

Bug description:
  wl driver is thriwing stack trace repeatdly in log

  avril 19 09:13:56 titan kernel: Hardware name: Dell Inc. Inspiron 
3521/06RYX8, BIOS A12 10/25/2013
  avril 19 09:13:56 titan kernel: RIP: 0010:cfg80211_roamed+0x217/0x230 
[cfg80211]
  avril 19 09:13:56 titan kernel: Code: 00 00 00 49 8d 4d 70 4c 89 f7 45 0f b6 
85 90 00 00 00 6a 02 48 8b 36 e8 37 8c fd ff 48 89 43 08 5a 48 85 c0 0f 8
  avril 19 09:13:56 titan kernel: RSP: 0018:ae46c150bdb0 EFLAGS: 00010246
  avril 19 09:13:56 titan kernel: RAX:  RBX: ae46c150be00 
RCX: 0002
  avril 19 09:13:56 titan kernel: RDX: 0002 RSI: fe01 
RDI: c07b92b4
  avril 19 09:13:56 titan kernel: RBP: ae46c150bde0 R08:  
R09: 
  avril 19 09:13:56 titan kernel: R10: ae46c150be00 R11: 9c7f769b4fba 
R12: 006000c0
  avril 19 09:13:56 titan kernel: R13: 9c7f77550c00 R14: 9c7f769b4300 
R15: dead0100
  avril 19 09:13:56 titan kernel: FS:  () 
GS:9c7f870c() knlGS:
  avril 19 09:13:56 titan kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  avril 19 09:13:56 titan kernel: CR2: 7ffc4c52bbe8 CR3: 000238ada001 
CR4: 001626e0
  avril 19 09:13:56 titan kernel: Call Trace:
  avril 19 09:13:56 titan kernel:  wl_bss_roaming_done.isra.25+0xd6/0x110 [wl]
  avril 19 09:13:56 titan kernel:  ? wl_bss_roaming_done.isra.25+0xd6/0x110 [wl]
  avril 19 09:13:56 titan kernel:  wl_notify_roaming_status+0x44/0x60 [wl]
  avril 19 09:13:56 titan kernel:  ? down_interruptible+0x33/0x60
  avril 19 09:13:56 titan kernel:  wl_event_handler+0x6c/0x150 [wl]
  avril 19 09:13:56 titan kernel:  kthread+0x120/0x140
  avril 19 09:13:56 titan kernel:  ? wl_notify_scan_status+0x230/0x230 

[Kernel-packages] [Bug 1825487] [NEW] The Realtek card reader does not enter PCIe 1.1/1.2

[Kai-Heng Feng]

Public bug reported:

[Impact]
The Realtek card reader does not enter PCIe 1.1/1.2.
This keeps Intel SoC staying at PC3, which consumes lots of power.

[Fix]
Set correct ASPM parameter on rtsx_pci.

[Test]
With the patch applied, Intel SoC can enter PC10, which saves lots of power.

[Regression Potential]
Low. The card reader in question still works as before.

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

Title:
  The Realtek card reader does not enter PCIe 1.1/1.2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The Realtek card reader does not enter PCIe 1.1/1.2.
  This keeps Intel SoC staying at PC3, which consumes lots of power.

  [Fix]
  Set correct ASPM parameter on rtsx_pci.

  [Test]
  With the patch applied, Intel SoC can enter PC10, which saves lots of power.

  [Regression Potential]
  Low. The card reader in question still works as before.

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

-- 
Mailing list: https://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 1825487] Missing required logs.

[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 1825487

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

Title:
  The Realtek card reader does not enter PCIe 1.1/1.2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The Realtek card reader does not enter PCIe 1.1/1.2.
  This keeps Intel SoC staying at PC3, which consumes lots of power.

  [Fix]
  Set correct ASPM parameter on rtsx_pci.

  [Test]
  With the patch applied, Intel SoC can enter PC10, which saves lots of power.

  [Regression Potential]
  Low. The card reader in question still works as before.

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

-- 
Mailing list: https://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 1825490] [NEW] Bug in the update of ubuntu 18.10 to 19.04

[Nicolas Barrat]

Public bug reported:

First in the upgrade I had a notification like the install-info were not
installed correctly. After, at the end after the next part of the
installation, they say that the upgrade has not been completed and that
a restauration will be made. Then a new page was opened to say that the
upgrade was made successfully. After this, everything was closed but the
part of the cleaning and restarting was not made so I restarted my
computer and I was on ubuntu 19.04 but a new notification said me that I
had software bug so I send the report.

(It was an upgrade from the last update of Ubuntu 18.10, I made an
update before the upgrade, to the 19.04)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nicolasb   1854 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 10:50:23 2019
InstallationDate: Installed on 2019-02-27 (50 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 04ca:706d Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ProBook 450 G5
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f6f4518b-e644-4545-86f7-061cb36bda20 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware1.178
SourcePackage: linux
StagingDrivers: r8822be
UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
dmi.bios.date: 01/03/2019
dmi.bios.vendor: HP
dmi.bios.version: Q85 Ver. 01.06.00
dmi.board.name: 837D
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.32.00
dmi.chassis.asset.tag: 5CD82354RB
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.06.00:bd01/03/2019:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.32.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 450 G5
dmi.product.sku: 1LU55AV
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug disco staging

** Attachment added: "Capture d’écran de 2019-04-19 10-44-52.png"
   
https://bugs.launchpad.net/bugs/1825490/+attachment/5256942/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202019-04-19%2010-44-52.png

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

Title:
  Bug in the update of ubuntu 18.10 to 19.04

Status in linux package in Ubuntu:
  New

Bug description:
  First in the upgrade I had a notification like the install-info were
  not installed correctly. After, at the end after the next part of the
  installation, they say that the upgrade has not been completed and
  that a restauration will be made. Then a new page was opened to say
  that the upgrade was made successfully. After this, everything was
  closed but the part of the cleaning and restarting was not made so I
  restarted my computer and I was on ubuntu 19.04 but a new notification
  said me that I had software bug so I send the report.

  (It was an upgrade from the last update of Ubuntu 18.10, I made an
  update before the upgrade, to the 19.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolasb   1854 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 10:50:23 2019
  InstallationDate: Installed on 2019-02-27 (50 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04ca:706d Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f6f4518b-e644-4545-86f7-061cb36bda20 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   l

[Kernel-packages] [Bug 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2

[Kai-Heng Feng]

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

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

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

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

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => 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/1825487

Title:
  The Realtek card reader does not enter PCIe 1.1/1.2

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  The Realtek card reader does not enter PCIe 1.1/1.2.
  This keeps Intel SoC staying at PC3, which consumes lots of power.

  [Fix]
  Set correct ASPM parameter on rtsx_pci.

  [Test]
  With the patch applied, Intel SoC can enter PC10, which saves lots of power.

  [Regression Potential]
  Low. The card reader in question still works as before.

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

-- 
Mailing list: https://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 1825490] Status changed to Confirmed

[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/1825490

Title:
  Bug in the update of ubuntu 18.10 to 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First in the upgrade I had a notification like the install-info were
  not installed correctly. After, at the end after the next part of the
  installation, they say that the upgrade has not been completed and
  that a restauration will be made. Then a new page was opened to say
  that the upgrade was made successfully. After this, everything was
  closed but the part of the cleaning and restarting was not made so I
  restarted my computer and I was on ubuntu 19.04 but a new notification
  said me that I had software bug so I send the report.

  (It was an upgrade from the last update of Ubuntu 18.10, I made an
  update before the upgrade, to the 19.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolasb   1854 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 10:50:23 2019
  InstallationDate: Installed on 2019-02-27 (50 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04ca:706d Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=f6f4518b-e644-4545-86f7-061cb36bda20 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.06.00
  dmi.board.name: 837D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.32.00
  dmi.chassis.asset.tag: 5CD82354RB
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.06.00:bd01/03/2019:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.32.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 450 G5
  dmi.product.sku: 1LU55AV
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1742626] Re: Unstable LTS kernel 4.13

[Josep Pujadas-Jubany]

Our systems are stable with later kernels:

uname -a
Linux xx-lubuntu 4.15.0-47-generic #50~16.04.1-Ubuntu SMP Fri Mar 15 
16:06:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

At home (were I have virtualbox) I switched to Oracle package to solve
the problem and I didn't revert my installation to the 16.04 package:

dpkg -l | grep virtualbox
ii  virtualbox-5.2  5.2.28-130011~Ubuntu~xenial 
 amd64Oracle VM VirtualBox

Thanks!

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

Title:
  Unstable LTS kernel 4.13

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe package in Ubuntu:
  Incomplete
Status in linux-lts-xenial package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  At job, after upgrading many Lubuntu 16.04 LTS 64 bit systems from
  4.10 to 4.13 they are (most of them) unstable.

  Acer TravelMate B117-M (SSD disk) freeze at boot or show errors at
  startup such:

  unexpected irq trap at vector

  similar to https://forum.manjaro.org/t/manjaro-kernel-4-13-unexpected-
  irq-trap-at-vector-e3-error/30942

  At home (no signed kernel, old machine) my VirtualBox freezes also the 
machine, as explained at 
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuari 1178 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6bcea77a-5eea-4993-87b7-5007d7816838
  InstallationDate: Installed on 2017-05-25 (246 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Acer TravelMate B117-M
  Package: linux-signed
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4472d672-c062-4877-b3ad-689003c70743 ro quiet splash
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-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.157.15
  Tags:  xenial
  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: 09/08/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Lepus_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd09/08/2016:svnAcer:pnTravelMateB117-M:pvrV1.11:rvnAcer:rnLepus_BA:rvrV1.11:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: TravelMate B117-M
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2

[AceLan Kao]

** Tags added: originate-from-1821890 somerville

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

Title:
  The Realtek card reader does not enter PCIe 1.1/1.2

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  [Impact]
  The Realtek card reader does not enter PCIe 1.1/1.2.
  This keeps Intel SoC staying at PC3, which consumes lots of power.

  [Fix]
  Set correct ASPM parameter on rtsx_pci.

  [Test]
  With the patch applied, Intel SoC can enter PC10, which saves lots of power.

  [Regression Potential]
  Low. The card reader in question still works as before.

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

-- 
Mailing list: https://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 1802306] Re: Network connectivity lost after a few minutes on Intel Corporation Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36

[Pirouette Cacahuète]

Just came accross this:
https://bugzilla.kernel.org/show_bug.cgi?id=199251

** Bug watch added: Linux Kernel Bug Tracker #199251
   https://bugzilla.kernel.org/show_bug.cgi?id=199251

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

Title:
  Network connectivity lost after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36

Status in linux package in Ubuntu:
  Expired

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1568211] Re: Unable to boot

[shadowvzs]

i also got black screen, indiferent ubuntu/linux mint/manjaro, kernel 4.15 or 
5.0...
only with nomodeset work with awfull resolution :( amd radeon rx vega 11

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

Title:
  Unable to boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  I upgraded overnight from Wily to Xenial. The system will not boot.
  Only a blank screen after grub loads the kernel.

  The recovery kernel loads fine and I was able to find the following
  messages:

  [drm] VGACON disable radeon kernel modesetting
  [drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!

  The recovery kernel command line had a nomodeset parameter that was
  not in the main kernel command line.

  Note: For what it's worth I reported a similar issue against several
  Utopic kernels (bug #1407505). There was a back and forth with
  jsalisbury until a kernel finally worked. I have had no problems until
  today.

  WORKAROUND: Adding the nomodeset parameter the main kernel command
  line finally booted the system.

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

-- 
Mailing list: https://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 1822829] Re: linux-snapdragon: 4.4.0-1111.116 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-.116/snapdragon-4.4-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux-snapdragon: 4.4.0-.116 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1822834
  phase: Testing
  phase-changed: Monday, 15. April 2019 02:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff

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

-- 
Mailing list: https://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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[layingback]

Also affected:  Ubuntu MATE 18.10 -> 19.04 Upgrade.  Normal system (not
VM).  18.10 was a hardly used clean install of Ubuntu MATE, up-to-date
patch status before update.  Install appears complete and OK ...

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

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

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions

-- 
Mailing list: https://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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Nemanja Vukosav]

Experiencing the same thing lately on Ubuntu 18.04.2 LTS ...

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in console-setup source package in Cosmic:
  New
Status in linux source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  New
Status in console-setup source package in Disco:
  In Progress
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  New
Status in linux source package in Eoan:
  New
Status in xorg-server source package in Eoan:
  New

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

-- 
Mailing list: https://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 1822829] Re: linux-snapdragon: 4.4.0-1111.116 -proposed tracker

[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: 1822834
- phase: Testing
- phase-changed: Monday, 15. April 2019 02:08 UTC
+ phase: Signoff
+ phase-changed: Friday, 19. April 2019 10:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

Title:
  linux-snapdragon: 4.4.0-.116 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1822834
  phase: Signoff
  phase-changed: Friday, 19. April 2019 10:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- security signoff not verified
security-signoff: Pending -- waiting for signoff

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

-- 
Mailing list: https://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 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15

[Po-Hsu Lin]

Probably a dup with bug 1822247.

Let's see if we can still see this in the next cycle.

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

Title:
  ubuntu_nbd_smoke_test failed with I/O error on X-4.15

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 4.15.0-45.48~16.04.1

  creating backing nbd image /tmp/nbd_image.img

  

  Image path:/tmp/nbd_image.img
  Mount point:   /mnt/nbd-test-25789
  Date:  Thu Jan 31 14:42:42 UTC 2019
  Host:  onibi
  Kernel:4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 
UTC 2019
  Machine:   onibi x86_64 x86_64
  CPUs online:   4
  CPUs total:4
  Page size: 4096
  Pages avail:   1351388
  Pages total:   2038431
  Free space:
  Filesystem  Size  Used Avail Use% Mounted on
  udev3.9G 0  3.9G   0% /dev
  tmpfs   797M   17M  780M   3% /run
  /dev/sda1   917G  9.1G  861G   2% /
  tmpfs   3.9G  4.0K  3.9G   1% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
  tmpfs   797M 0  797M   0% /run/user/1000
  tmpfs   100K 0  100K   0% /var/lib/lxd/shmounts
  tmpfs   100K 0  100K   0% /var/lib/lxd/devlxd
  cgmfs   100K 0  100K   0% /run/cgmanager/fs
  


  NBD device /dev/nbd0 created
  found nbd export
  NBD exports found:
  test
  starting client with NBD device /dev/nbd0
  Negotiation: ..size = 128MB
  creating ext4 on /dev/nbd0
  mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  checking ext4 on /dev/nbd0
  fsck from util-linux 2.27.1
  /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks

  mount:
  /dev/nbd0 on /mnt/nbd-test-25789 type ext4 (rw,relatime,data=ordered)
  mounted on /dev/nbd0

  free:
  Filesystem 1K-blocks  Used Available Use% Mounted on
  /dev/nbd0 122835  1550112111   2% /mnt/nbd-test-25789

  creating large file /mnt/nbd-test-25789/largefile
  -rw-r--r-- 1 root root 100M Jan 31 14:42 /mnt/nbd-test-25789/largefile

  free:
  Filesystem 1K-blocks   Used Available Use% Mounted on
  /dev/nbd0 122835 103951  9710  92% /mnt/nbd-test-25789

  removing file /mnt/nbd-test-25789/largefile
  unmounting /mnt/nbd-test-25789
  stopping client
  disconnect, sock, done
  Found kernel warning, IO error and/or call trace
  echo
  [ 4593.254552] creating backing nbd image /tmp/nbd_image.img
  [ 4595.506134] NBD device /dev/nbd0 created
  [ 4595.557990] found nbd export
  [ 4596.604855] starting client with NBD device /dev/nbd0
  [ 4596.606795] creating ext4 on /dev/nbd0
  [ 4597.013721] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
  [ 4597.390241] checking ext4 on /dev/nbd0
  [ 4597.455371] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
  [ 4597.460552] mounted on /dev/nbd0
  [ 4597.461810] creating large file /mnt/nbd-test-25789/largefile
  [ 4599.056704] removing file /mnt/nbd-test-25789/largefile
  [ 4599.276298] unmounting /mnt/nbd-test-25789
  [ 4600.319460] stopping client
  [ 4600.320083] block nbd0: NBD_DISCONNECT
  [ 4600.320127] block nbd0: shutting down sockets
  [ 4600.320267] nbd0: detected capacity change from 0 to 134217728
  [ 4600.320306] print_req_error: 7 callbacks suppressed
  [ 4600.320308] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.325890] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.333002] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.338653] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.345687] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.351253] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.358279] ldm_validate_partition_table(): Disk read failed.
  [ 4600.358305] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.363892] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.371075] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.376645] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.383687] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.389230] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.396307] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.401819] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.408826] Dev nbd0: unable to read RDB block 0
  [ 4600.413467] print_req_error: I/O error, dev nbd0, sector 0
  [ 4600.418955] Buffer I/O error on dev nbd0, logical block 0, async page read
  [ 4600.425858] print_req_error: I/O error, dev nbd0, sector 24
  [ 4600.431433] Buffer I/O error on 

[Kernel-packages] [Bug 1742626] Re: Unstable LTS kernel 4.13

[Po-Hsu Lin]

OK!
Thanks for the feedback, I am gonna close this bug.
Please feel free to open a new report if you have encountered any issue.

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

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

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

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

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

Title:
  Unstable LTS kernel 4.13

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-signed package in Ubuntu:
  Invalid

Bug description:
  At job, after upgrading many Lubuntu 16.04 LTS 64 bit systems from
  4.10 to 4.13 they are (most of them) unstable.

  Acer TravelMate B117-M (SSD disk) freeze at boot or show errors at
  startup such:

  unexpected irq trap at vector

  similar to https://forum.manjaro.org/t/manjaro-kernel-4-13-unexpected-
  irq-trap-at-vector-e3-error/30942

  At home (no signed kernel, old machine) my VirtualBox freezes also the 
machine, as explained at 
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuari 1178 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6bcea77a-5eea-4993-87b7-5007d7816838
  InstallationDate: Installed on 2017-05-25 (246 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Acer TravelMate B117-M
  Package: linux-signed
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4472d672-c062-4877-b3ad-689003c70743 ro quiet splash
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-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.157.15
  Tags:  xenial
  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: 09/08/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Lepus_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd09/08/2016:svnAcer:pnTravelMateB117-M:pvrV1.11:rvnAcer:rnLepus_BA:rvrV1.11:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: TravelMate B117-M
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1799019] Re: Linux crashed so severly that I have to reinstall.

[Po-Hsu Lin]

Hello,
my apology for this situation, we let this package (linux-signed) slip through 
our radar in the old days. The process has been improved now.

I am gonna close this bug with Invalid, but please feel free to open a
new bug with command "ubuntu-bug linux" base on what you have
encountered recently (preferably one issue in a report, and with a
supported version, as Ubuntu Mate 14.10 has already reaches it End-of-
Life [1]).

Or ask questions on community forums like https://askubuntu.com
https://ubuntuforums.org/

Thank you.

[1] https://en.wikipedia.org/wiki/Ubuntu_MATE

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

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

Title:
  Linux crashed so severly that I have to reinstall.

Status in linux-signed package in Ubuntu:
  Invalid

Bug description:
  First Google Chrome and Chromium crashed closing all their windows.
  Then most, but not all, of the VisualWorks windows diappeared.
  (Unfortunately the System window closed so I could not exit properly).
  Then the list of open windows at the bottom of the screen disappeared,
  as did the menu bar at the top. With no menu to shutdown, I had to
  turn power off.

  When I tried to reboot I got the Ubuntu symbol and the progress dots
  underneath. After more than an hour, I got a command line to log in.
  (Not a terminal window - Ubuntu never started.)

  I was able to log in but could do nothing since this was a system
  without MATE or any window GUI.

  Every time I try to reboot, I get the save progress dots for over an
  hour and then the terminal mode login prompt.

  I had to boot from the distribution DVD to make this report before re-
  installing the system.

  Please fix your documentation on reporting system crashes. What is
  "apport" and how do I run it?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: MATE
  Date: Sun Oct 21 02:13:33 2018
  LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1770006] Re: Test Bug

[Po-Hsu Lin]

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

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

Title:
  Test Bug

Status in linux-signed package in Ubuntu:
  Invalid

Bug description:
  Test bug reported by jsalisbury.

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

-- 
Mailing list: https://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 1823015] Re: Ubuntu 14.04 crashes after a period of keyboard inactivity

[Po-Hsu Lin]

Hello James,
is it possible to collect the kernel panic message? (screenshots or etc.)

Thanks

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

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

Title:
  Ubuntu 14.04 crashes after a period of keyboard inactivity

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  After the update to kernel Linux 3.13.0-149 generic  Ubuntu 14.4 crashes 
after a period of keyboard inactivity . The period is about 1 hour .The crash  
takes one to a terminal type screen which gives some kernel panic information . 
At this point the PC has to be physically switched off and restarted. Ubuntu 
14.4  crashes on all  subsequent Kernel updates upto and including  3.13.0-168  
.
  I now think the crash is connected with the power setting on the PC -   
'Power .Suspend when inactive for : nn minutes/hours '.  
  On 3.13.0-168 when the power setting  are ' do not suspend' Ubuntu does not 
crash . I have not tested this on earlier kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-168-generic 3.13.0-168.218
  ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-168-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  3 16:31:18 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  InstallationDate: Installed on 2016-02-02 (1155 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to trusty on 2016-07-08 (998 days ago)

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

-- 
Mailing list: https://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 1824520] Re: Unable to turn off the airplane mode with wireless key on Dell M3800

[Kai-Heng Feng]

Both AT Keyboard and Dell-RBTN emit wireless hotkey event. I think we
should handle this in kernel to let only one driver to handle the event.

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

Title:
  Unable to turn off the airplane mode with wireless key on Dell M3800

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The airplane mode can be activated with the wireless key combination on this 
laptop (fn + PrtScn)
  You will see the "Airplane mode enabled" notification, and the BT / Wireless 
turned off accordingly.

  However the same key combination cannot turn the wireless back on.
  You will see the "Airplane mode disabled" notification followed by the 
"Airplane mode enabled" message. 

  It feels a bit like a repeat-key issue.
  But the evtest shows the identical result:

  * Turn on the airplane mode:
  Event: time 1555070280.383302, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1
  Event: time 1555070280.383302, -- SYN_REPORT 
  Event: time 1555070280.383327, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0
  Event: time 1555070280.383327, -- SYN_REPORT 

  * Turn off the airplane mode:
  Event: time 1555070325.562502, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1
  Event: time 1555070325.562502, -- SYN_REPORT 
  Event: time 1555070325.562514, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0
  Event: time 1555070325.562514, -- SYN_REPORT 

  dmesg for turning on the airplane mode:
  Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Starting Load/Save RF Kill 
Switch Status...
  Apr 12 08:03:53 u-Dell-Precision-M3800 kernel: [ 1229.634982] wlp6s0: 
deauthenticating from 18:9c:5d:31:3f:e0 by local choice (Reason: 
3=DEAUTH_LEAVING)
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4574] manager: rfkill: WiFi now disabled by radio killswitch
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4581] device (wlp6s0): state change: activated -> unavailable 
(reason 'none', sys-iface-state: 'managed')
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4590] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 
6521
  Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]:   
[1555070633.4590] dhcp4 (wlp6s0): state changed bound -> done
  Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Started Load/Save RF Kill 
Switch Status.
  Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: wlp6s0: 
CTRL-EVENT-DISCONNECTED bssid=18:9c:5d:31:3f:e0 reason=3 locally_generated=1
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface 
wlp6s0.IPv6 no longer relevant for mDNS.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS 
multicast group on interface wlp6s0.IPv6 with address fe80::bb23:69c3:d7b9:f6df.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface 
wlp6s0.IPv4 no longer relevant for mDNS.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS 
multicast group on interface wlp6s0.IPv4 with address 10.101.46.102.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address 
record for fe80::bb23:69c3:d7b9:f6df on wlp6s0.
  Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address 
record for 10.101.46.102 on wlp6s0.
  Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft 
blocked
  Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot 
reach: https://daisy.ubuntu.com
  Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] offline
  Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft 
blocked
  Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot 
reach: https://daisy.ubuntu.com
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf
  Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 
127.0.0.53#53
  Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: nl80211: deinit 
ifname=p2p-dev-wlp6s0 disabled_11b_rates=0
  Apr 12 08:03:53 u-Dell-Precision-M3800 gsd-sharing[18

[Kernel-packages] [Bug 1821903] Re: svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4

[Thadeu Lima de Souza Cascardo]

I fixed the issue with tsc-adjust on kvm-unit-tests itself, sent
upstream, fixed on our disco branch. That should fix it for 4.4 kernels
as well, though I only tested on 5.0 kernels for now. Trusty likely
needs further review.

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

Title:
  svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux-signed-lts-xenial source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-signed-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-signed-lts-xenial source package in Cosmic:
  Invalid

Bug description:
  This svm test timeouted on T-3.13
  failed on T-4.4 with:

  
root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
  TESTNAME=svm TIMEOUT=90s ACCEL= ./x86/run x86/svm.flat -smp 2 -cpu qemu64,+svm
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/svm.flat -smp 
2 -cpu qemu64,+svm # -initrd /tmp/tmp.PDi0UKyCcl

  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 466000
  cr4 = 20
  PASS: null
  PASS: vmrun
  PASS: ioio
  PASS: vmrun intercept check
  PASS: cr3 read intercept
  PASS: cr3 read nointercept
  PASS: cr3 read intercept emulate
  PASS: dr intercept check
  PASS: msr intercept check
  PASS: mode_switch
  PASS: asid_zero
  PASS: sel_cr0_bug
  FAIL: tsc_adjust
  Latency VMRUN : max: 80562 min: 19763 avg: 20374
  Latency VMEXIT: max: 83146 min: 20193 avg: 20834
  PASS: latency_run_exit
  Latency VMLOAD: max: 38298 min: 4619 avg: 4838
  Latency VMSAVE: max: 32870 min: 4637 avg: 4809
  Latency STGI:   max: 55478 min: 3846 avg: 3923
  Latency CLGI:   max: 67473 min: 3379 avg: 3437
  PASS: latency_svm_insn
  SUMMARY: 15 tests, 1 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
  ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Mar 27 11:00:42 2019
  SourcePackage: linux-signed-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+subscriptions

-- 
Mailing list: https://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 1821903] Re: svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4

[Thadeu Lima de Souza Cascardo]

The upstream submission:
https://marc.info/?l=kvm&m=155561857003690&w=2

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

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

** Changed in: linux-signed-lts-xenial (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-signed-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-signed-lts-xenial (Ubuntu Cosmic)
   Status: New => Invalid

** Tags added: verification-needed verification-needed-xenial

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

Title:
  svm in ubuntu_kvm_unit_test failed on 3.13 / 4.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux-signed-lts-xenial source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-signed-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-signed-lts-xenial source package in Cosmic:
  Invalid

Bug description:
  This svm test timeouted on T-3.13
  failed on T-4.4 with:

  
root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests#
  TESTNAME=svm TIMEOUT=90s ACCEL= ./x86/run x86/svm.flat -smp 2 -cpu qemu64,+svm
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/svm.flat -smp 
2 -cpu qemu64,+svm # -initrd /tmp/tmp.PDi0UKyCcl

  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 466000
  cr4 = 20
  PASS: null
  PASS: vmrun
  PASS: ioio
  PASS: vmrun intercept check
  PASS: cr3 read intercept
  PASS: cr3 read nointercept
  PASS: cr3 read intercept emulate
  PASS: dr intercept check
  PASS: msr intercept check
  PASS: mode_switch
  PASS: asid_zero
  PASS: sel_cr0_bug
  FAIL: tsc_adjust
  Latency VMRUN : max: 80562 min: 19763 avg: 20374
  Latency VMEXIT: max: 83146 min: 20193 avg: 20834
  PASS: latency_run_exit
  Latency VMLOAD: max: 38298 min: 4619 avg: 4838
  Latency VMSAVE: max: 32870 min: 4637 avg: 4809
  Latency STGI:   max: 55478 min: 3846 avg: 3923
  Latency CLGI:   max: 67473 min: 3379 avg: 3437
  PASS: latency_svm_insn
  SUMMARY: 15 tests, 1 unexpected failures

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2
  ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Wed Mar 27 11:00:42 2019
  SourcePackage: linux-signed-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821903/+subscriptions

-- 
Mailing list: https://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

[Po-Hsu Lin]

4.15.0-48.51 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kernel_selftests - global.get_metadata in seccomp (bug 1811057) 
raw_skew in timer (bug 1811194)
  ubuntu_kvm_unit_tests - apic-split timeouted (bug 1821390) apic timeouted 
(bug 1748103) svm (bug 1821903)
  ubuntu_ltp - binfmt_misc02 (bug 1822246)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  ubuntu_nbd_smoke_test - bug 1822247
  xfstests - timed out on ext4 generic/430 test (bug 1755999)

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) 
global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194)
  ubuntu_kvm_unit_tests - gicv3-ipi and gicv3-active failed on Moonshot (bug 
1790825)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  xfstests - timed out on ext4 generic/430 test (bug 1755999)

47 / 48 tests were run, missing: xfstests
Issue to note in i386:
  ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578)
  ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) 
global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) 
Kprobe event string type argument in ftrace (bug 1812645)
  ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056)
  ubuntu_kvm_unit_tests - all 29 test failed on i386 (bug 1822235)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)

Issue to note in ppc64le (P8):
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) 
TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) 
global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) 
ebb in powerpc (bug 1812805) Kprobe event argument syntax in ftrace (bug 
1812809)
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) 
fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116)
  xfstests - timed out on ext4 generic/430 test (bug 1755999)

48 / 49 tests were run, missing: xfstests
Issue to note in ppc64le (P9):
  hwclock - hwclock test failed on PowerPC due to 0.x sec difference (bug 
1802233)
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) 
TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) 
global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) 
ebb in powerpc (bug 1812805) tm-unavailable in powerpc (bug 1813129)
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) 
fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116)
  ubuntu_nbd_smoke_test - bug 1822247

Test case ubuntu_ramfs_stress does not exist in the database, please check
41 / 48 tests were run, missing: ubuntu_boot, ubuntu_bpf, ubuntu_bpf_jit, 
ubuntu_btrfs_kernel_fixes, ubuntu_cts_kernel, ubuntu_stress_smoke_test, 
ubuntu_zfs_fstest, ubuntu_zfs_xfs_generic
Issue to note in s390x:
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 
1811057) ftrace (bug 1812836)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594)
  ubuntu_nbd_smoke_test - bug 1822247

46 / 48 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes
Issue to note in s390x (Ubuntu on LPAR):
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 
1811057) ftrace (bug 1812836)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is 
defined (bug 1788574)

46 / 48 tests were run, missing: ubuntu_boot, ubuntu_btrfs_kernel_fixes
Issue to note in s390x (zVM):
  ubuntu_bpf - test_map failed (bug 1788562)
  ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) 
TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 
1811057) ftrace (bug 1812836)
  ubuntu_kvm_unit_tests - skey failed (bug 1778705)
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
sync_file_range02 (bug 1819116)
  ubuntu_lxc - Container "reboot" is defined (bug 1788574)

Note: No xfstests for P9 as it does not have a scratch drive
Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860)
Note: s390x KVM test result incomplete due to infrastructure migration


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

** Changed in: kernel-sru-workflow/regression

[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker

[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 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe)
  derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822808 
(linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 
(linux-oracle), bug 1822981 (linux), bug 1823254 (linux), bug 1823755 
(linux-gke-4.15), bug 1824204 (linux-snapdragon), bug 1824592 (linux-fips), bug 
1824773 (linux-aws)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 15:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   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/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:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  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 1822808 
(linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 
(linux-oracle), bug 1822981 (linux), bug 1823254 (linux), bug 1823755 
(linux-gke-4.15), bug 1824204 (linux-snapdragon), bug 1824592 (linux-fips), bug 
1824773 (linux-aws)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 15:30 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/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 1769792] Re: Keyboard and Touchpad do not work after suspend/resume

[Alessio Boccialoni]

I have the same problem, with Fujitsu Lifebook E557, Ubuntu 18.10,
kernel 4.18.0-17-generic.

After resume from suspend, touchpad doesn't work at all. Keyboard works
somewhat, but some keys are randomly "repete". Reboot doesn't
help, but need to to turn the machine off and on 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/1769792

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial

[Nicolas Dichtel]

root@ubuntu1604:~# dpkg --list | grep iproute2
ii  iproute2 4.3.0-1ubuntu3.16.04.4
amd64networking and traffic control tools
root@ubuntu1604:~# apt-get install iproute2/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '4.3.0-1ubuntu3.16.04.5' (Ubuntu:16.04/xenial-proposed 
[amd64]) for 'iproute2'
Suggested packages:
  iproute2-doc
The following packages will be upgraded:
  iproute2
1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
Need to get 523 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 iproute2 
amd64 4.3.0-1ubuntu3.16.04.5 [523 kB]
Fetched 523 kB in 0s (6,782 kB/s)
(Reading database ... 85262 files and directories currently installed.)
Preparing to unpack .../iproute2_4.3.0-1ubuntu3.16.04.5_amd64.deb ...
Unpacking iproute2 (4.3.0-1ubuntu3.16.04.5) over (4.3.0-1ubuntu3.16.04.4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up iproute2 (4.3.0-1ubuntu3.16.04.5) ...
root@ubuntu1604:~# dpkg --list | grep iproute2
ii  iproute2 4.3.0-1ubuntu3.16.04.5
amd64networking and traffic control tools
root@ubuntu1604:~# ip link add dev dummy0 type dummy
RTNETLINK answers: File exists
root@ubuntu1604:~# ip link add dev dummy1 type dummy
root@ubuntu1604:~# ip link set dev dummy0 up
root@ubuntu1604:~# ip link set dev dummy1 up
root@ubuntu1604:~# tc qdisc add dev dummy0 handle 1: root prio
root@ubuntu1604:~# tc filter add dev dummy0 parent 1: matchall skip_hw action 
mirred egress mirror dev dummy1
root@ubuntu1604:~# tc filter show dev dummy0
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1

root@ubuntu1604:~#

=> test is OK.

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

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]

  == Impact ==
  The Xenial 4.4 kernel already has a patch applied which implements the 
matchall filter. But in order to actually use it, iproute2 needs to pick up the 
user-space
  side of the implementation.

  == Fix ==
  Backported a patch from iproute2 upstream which adds the missing support. 
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).

  == Risk of Regression ==
  This adds a new filter type which has to be actively selected. This should 
not impact existing uses. So low.

  == Testcase ==
  ip link add dev dummy0 type dummy
  ip link add dev dummy1 type dummy
  ip link set dev dummy0 up
  ip link set dev dummy1 up
  tc qdisc add dev dummy0 handle 1: root prio
  tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress 
mirror dev dummy1

  at this point, "tc filter show dev dummy0" should spit out something
  like:

  filter parent 1: protocol all pref 49152 matchall 
  filter parent 1: protocol all pref 49152 matchall handle 0x1 
  action order 1: mirred (Egress Mirror to device dummy1) pipe
  index 1 ref 1 bind 1
   
  and the functionality can be tested via

  tcpdump -n -i dummy1 &
  ping -I dummy0 1.2.3.4

  ---

  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

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

-- 
Mailing list: https://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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[fredm]

The instructions in comments #44 and #45 totally solved this for me!
Thank you.

Further, I think my machine is now going to sleep more reliably :)

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

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

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1806681] Re: hp_wmi: query 0xd returned error 0x5

[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/1806681

Title:
  hp_wmi: query 0xd returned error 0x5

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

Bug description:
  Hello,

  dmesg:
  [   18.296366] hp_wmi: query 0xd returned error 0x5

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:05:38 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

Just reproduced it on my env (where things used to work) after updating
from MAAS 2.5.0~rc2 to 2.5.2.

https://paste.ubuntu.com/p/CY834ZGnvS/
[   15.458594] VFS: Cannot open root device 
"squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bion"; or 
unknown-block(0,0): error -6

tree /var/lib/maas/boot-resources/
/var/lib/maas/boot-resources/
# ...

├── current -> snapshot-20190419-115735
└── snapshot-20190419-115735


Which binaries do I need to have uploaded?

sha256sum 
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/*
69ca457a119fe309d315972ca2756a17bd9bc55bc98f2bea5542566a7f41b08f  
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/boot-initrd
166853ad9342fdf5be17988e5e18cbf0458ab0da94f18f5e331b3581e3610b97  
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/boot-kernel
1e7841d7fca13ef27c2742cfc2c3a2d59491a74c268b705a02eb4ee8f673d150  
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/squashfs


ii  seabios1.10.2-1ubuntu1  
   all  Legacy BIOS implementation
ii  ipxe-qemu  
1.0.0+git-20180124.fbe8c52d-0ubuntu2.2  all 
 PXE boot firmware - ROM images for qemu
ii  qemu-kvm   1:2.11+dfsg-1ubuntu7.12  
   amd64QEMU Full virtualization on x86 
hardware
ii  libvirt0:amd64 4.0.0-1ubuntu8.8 
   amd64library for interfacing with 
different virtualization systems

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

-- 
Mailing list: https://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 1758442] Re: [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

[Marcel Munce]

I also see those errors. Additionally "hp_wmi: query 0x4 returned error 0x5".
My grub configuration is untouched!

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

Title:
  [HP WMI] Issues with brightness keys [HP ProBook 640 G1]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Three of the "function" keys on this laptop don't work at all: "Mute",
  "Brightness Down", and "Brightness Up". I believe these keys are
  controlled by WMI. Other buttons not controlled by WMI, such as
  "Volume Up" and "Volume Down" (both by ACPI), work fine. Setting
  display brightness via software (e.g., GUI slider) works fine.

  Sometimes other keys (Windows, up/down arrow, pgup/pgdn) are
  interpreted as "Brightness Down". This behavior seems to come and go
  randomly after each reboot.

  I have tried setting (separately) acpi_osi=Linux and
  acpi_backlight=vendor without effect.

  The hp_wmi driver raises these message at each boot:
  [   19.610528] hp_wmi: query 0xd returned error 0x5
  [   19.610569] input: HP WMI hotkeys as /devices/virtual/input/input14

  This system has the latest BIOS (1.43A, released 2018-01-25) and the
  latest Intel ME firmware (9.1.42.3002, released 2017-12-19).

  No output is generated when pressing these buttons with evtest
  (choosing option 8, "HP WMI hotkeys"), xev, or acpi_listen).

  I have attached the debugging information requested at
  
,
  although fwts method does not seem to be a valid command (anymore?).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1415 F pulseaudio
   /dev/snd/controlC0:  vectro 1415 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Mar 23 17:15:19 2018
  HibernationDevice: RESUME=UUID=0f34a9a4-0160-489a-9325-45913b03eb06
  InstallationDate: Installed on 2018-03-23 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash acpi_osi=Linux vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend

[Ghanshyam]

I got this bug too after upgrading to 19.04 release with nvidia driver 418.
I see the corruption in lock screen and desktop background.

Additionally, if VS Code is open, terminal window in the vs code becomes
blank. This used to happen in 18.10 as well. Not sure if it's related
but just as additional info if it helps.

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 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
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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/gnome-shell/+bug/1809407/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post t

[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi

[Paolo Pisati]

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

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

Title:
  Load average inexplicably high with 5.0 kernel on rpi

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
  2019 aarch64 aarch64 aarch64 GNU/Linux

  I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
  After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
  ubuntu@ubuntu:~$ w
   19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

  /proc/loadavg is consistent with these numbers. But when I check top,
  there are no obvious culprits hogging the cpu or anything. Typically
  everything looks to be <1% cpu usage, with top being the biggest cpu
  hog at about 2%. The system doesn't seem too slow (for a pi), but it's
  unusual to see such high numbers.

  Nothing seems to be swapping:

  ubuntu@ubuntu:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:908 173 422   6 312 
707
  Swap: 0   0   0

  
  ubuntu@ubuntu:~$ iostat
  Linux 5.0.0-1006-raspi2 (ubuntu)  04/17/19_aarch64_   (4 CPU)

  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 1.640.151.572.060.00   94.57

  Device tpskB_read/skB_wrtn/skB_readkB_wrtn
  loop0 0.08 0.50 0.00354  0
  loop1 2.56 3.98 0.00   2805  0
  loop2 0.01 0.01 0.00  4  0
  mmcblk0  12.70   367.40   705.16 258830 496785

  ubuntu@ubuntu:~$ vmstat 1
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0  0  0 514540  18004 2240720097   182 2564   76  2  2 94  2 
 0
   0  0  0 514512  18004 22413600 0  2012 10136  142  0  0 94  
5  0
   0  0  0 514512  18004 22413600 0 0 10117  106  0  0 100  
0  0
   0  0  0 514512  18004 22413600 0 0 10121   98  0  0 100  
0  0
   0  0  0 514512  18012 22412800 0  2028 10129  141  0  0 93  
7  0
   0  0  0 514512  18012 22413600 0 0 10149  135  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0 0 10108   97  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0  2012 10125  126  0  0 95  
5  0
   0  0  0 514512  18012 22413600 0 0 10117  101  0  0 100  
0  0
   0  1  0 514512  18012 22413600 0  2012 10109  104  0  0 98  
2  0
   0  0  0 514512  18020 22412800 012 10139  150  0  0 96  
4  0
   0  0  0 514512  18020 22412800 0 0 10108   90  0  0 100  
0  0

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

-- 
Mailing list: https://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 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi

[Paolo Pisati]

I can reproduce the bug on a fresh installation of Disco/armhf rpi3.

Moreover, the bug appears to be kernel in-kernel - by installing the
Disco kernel on a Bionic image (that didn't show any abnormal load with
its Bionic/armhf kernel), the bug appears there too.

The bug is reproducible as early as Ubuntu-raspi2-5.0.0-1002.2, and
before that there's the Broadcom BSP, and the initial config sync wrt
bcm2709_defconfig - bisecting the Broadcom BSP is a bit problematic,
because removing patches, often, breaks the build.

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

Title:
  Load average inexplicably high with 5.0 kernel on rpi

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
  2019 aarch64 aarch64 aarch64 GNU/Linux

  I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
  After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
  ubuntu@ubuntu:~$ w
   19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

  /proc/loadavg is consistent with these numbers. But when I check top,
  there are no obvious culprits hogging the cpu or anything. Typically
  everything looks to be <1% cpu usage, with top being the biggest cpu
  hog at about 2%. The system doesn't seem too slow (for a pi), but it's
  unusual to see such high numbers.

  Nothing seems to be swapping:

  ubuntu@ubuntu:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:908 173 422   6 312 
707
  Swap: 0   0   0

  
  ubuntu@ubuntu:~$ iostat
  Linux 5.0.0-1006-raspi2 (ubuntu)  04/17/19_aarch64_   (4 CPU)

  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 1.640.151.572.060.00   94.57

  Device tpskB_read/skB_wrtn/skB_readkB_wrtn
  loop0 0.08 0.50 0.00354  0
  loop1 2.56 3.98 0.00   2805  0
  loop2 0.01 0.01 0.00  4  0
  mmcblk0  12.70   367.40   705.16 258830 496785

  ubuntu@ubuntu:~$ vmstat 1
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0  0  0 514540  18004 2240720097   182 2564   76  2  2 94  2 
 0
   0  0  0 514512  18004 22413600 0  2012 10136  142  0  0 94  
5  0
   0  0  0 514512  18004 22413600 0 0 10117  106  0  0 100  
0  0
   0  0  0 514512  18004 22413600 0 0 10121   98  0  0 100  
0  0
   0  0  0 514512  18012 22412800 0  2028 10129  141  0  0 93  
7  0
   0  0  0 514512  18012 22413600 0 0 10149  135  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0 0 10108   97  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0  2012 10125  126  0  0 95  
5  0
   0  0  0 514512  18012 22413600 0 0 10117  101  0  0 100  
0  0
   0  1  0 514512  18012 22413600 0  2012 10109  104  0  0 98  
2  0
   0  0  0 514512  18020 22412800 012 10139  150  0  0 96  
4  0
   0  0  0 514512  18020 22412800 0 0 10108   90  0  0 100  
0  0

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

-- 
Mailing list: https://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 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

[Manoj Iyer]

We see unknown chipset errors in 4.15 GA kernel in Bionic, but the
missing firmware issue is now fixed in bionic. We have support for this
Nvidia GPU in the bionic (4.18) HWE kernel and so I am marking this as
verification-done.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-se

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

echo -n 
'BOOT_IMAGE=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-kernel
 nomodeset ro 
root=squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
 ip=maas-vhost6:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc 
cloud-config-url=http://10.10.101.2:5248/MAAS/metadata/latest/by-id/xeqrrw/?op=get_preseed
 apparmor=0 log_host=10.10.101.2 log_port=5247 --- console=ttyS0,115200 
initrd=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-initrd
 BOOTIF=01-52-54-00-3f-ae-46' | wc -c
576

arch/x86/include/asm/setup.h:

#define COMMAND_LINE_SIZE 2048
#define PARAM_SIZE 4096 /* sizeof(struct boot_params) */


Doesn't look like we are any close to the kernel limits on parameters.

However, the root argument as printed in the panic message looks like a
64-byte string (last byte for null termination):

echo -n 'squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bion' | wc 
-c
63


It looks like this is coming from the following code (strlcpy into a 64-byte 
array):

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/init/do_mounts.c?id=Ubuntu-4.15.0-47.50#n42

static char __initdata saved_root_name[64];

static int __init root_dev_setup(char *line)
{
strlcpy(saved_root_name, line, sizeof(saved_root_name));
return 1;
}

__setup("root=", root_dev_setup);


And the overall code-path (judging by the md auto-detection log messages):

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/init/do_mounts.c?id=Ubuntu-4.15.0-47.50#n545
prepare_namespace -> 

if (saved_root_name[0]) {
root_device_name = saved_root_name;   // < (!) usage of a 
cut-down root param
if (!strncmp(root_device_name, "mtd", 3) ||
!strncmp(root_device_name, "ubi", 3)) {
mount_block_root(root_device_name, root_mountflags);

Does not look like we are hitting either EACCES or EINVAL and so we fall
through to panic():

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/init/do_mounts.c?id=Ubuntu-4.15.0-47.50#n381
void __init mount_block_root(char *name, int flags)
// ...
for (p = fs_names; *p; p += strlen(p)+1) {
int err = do_mount_root(name, p, flags, root_mount_data);
switch (err) {
case 0:
goto out;
case -EACCES:
case -EINVAL:
continue;
}
/*
 * Allow the user to distinguish between failed sys_open
 * and bad superblock on root device.
 * and give them a list of the available devices
 */
#ifdef CONFIG_BLOCK
__bdevname(ROOT_DEV, b);
#endif
printk("VFS: Cannot open root device \"%s\" or %s: error %d\n",
root_device_name, b, err);
printk("Please append a correct \"root=\" boot option; here are 
the available partitions:\n");

printk_all_partitions();
#ifdef CONFIG_DEBUG_BLOCK_EXT_DEVT
printk("DEBUG_BLOCK_EXT_DEVT is enabled, you need to specify "
   "explicit textual name for \"root=\" boot option.\n");
#endif
panic("VFS: Unable to mount root fs on %s", b);

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

-- 
Mailing list: https://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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

The kernel code path mentioned in #55 is only executed if there is no
"early userspace init" - in other words, if there is no /init on initrd:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/init/main.c?id=Ubuntu-4.15.0-47.50#n1087

/*
 * check if there is an early userspace init.  If yes, let it do all
 * the work
 */

if (!ramdisk_execute_command)
ramdisk_execute_command = "/init";  // <--- if there's no 
command specified, default to /init

if (sys_access((const char __user *) ramdisk_execute_command, 0) != 0) 
{  // <-- check if /init is present by doing the access syscall
ramdisk_execute_command = NULL;
prepare_namespace();  // <-- call prepare_namespace as 
mentioned in #55 which results in an error
}


However, I can see that the initrd used in my case contains the init script (so 
sys_access should be successful):

initrd=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily
/boot-initrd

 lsinitramfs 
/var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily/boot-initrd
 | grep -P ^init$
init

If I increase the memory allocation from 2048 to 2049 MiB the machine
starts to boot just fine.

Unsuccessful boot log (2048 MiB): https://paste.ubuntu.com/p/CY834ZGnvS/
Successful boot log (2049 MiB): https://paste.ubuntu.com/p/3fYfFXW8qR/

Attached boot-initrd.


** Attachment added: "boot-initrd"
   
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5257069/+files/boot-initrd

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

-- 
Mailing list: https://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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

I cannot reproduce the same with a xenial (GA kernel) image with 2048
MiB of RAM allocated to a VM.

So it seems to me that this is a kernel issue.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

-- 
Mailing list: https://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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

Found something interesting.

Bionic + 2048 MiB of RAM (bad):

[1.520243] Unpacking initramfs...
[   14.712821] Initramfs unpacking failed: broken padding
[   14.723088] Freeing initrd memory: 56636K

Bionic + 2049 MiB of RAM (good):

[0.752624] Unpacking initramfs...
[5.572407] Freeing initrd memory: 56636K

Xenial HWE + 2048 MiB of RAM (bad):

[5.598647] Unpacking initramfs...
[   84.494431] Initramfs unpacking failed: junk in compressed archive
[   84.503565] Freeing initrd memory: 54564K

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

-- 
Mailing list: https://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 1825554] [NEW] Ryzen5 2500U Vega 8 raven ridge flickering screen

[Lukas Wiest]

Public bug reported:

Hey,

I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR.
My display is flickering, depending on the displayed content in different 
frequency.

Video of the symptom: 
https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
--- 
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-11-09 (160 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Package: linux (not installed)
Tags:  cosmic
Uname: Linux 5.0.0-05-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 users vboxusers 
wireshark
_MarkForUpload: True

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


** Tags: apport-collected cosmic

** Tags added: apport-collected cosmic

** Description changed:

  Hey,
  
  I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR.
  My display is flickering, depending on the displayed content in different 
frequency.
  
- Video of the symptom:
- https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
+ Video of the symptom: 
https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.2
+ Architecture: amd64
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-11-09 (160 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: linux (not installed)
+ Tags:  cosmic
+ Uname: Linux 5.0.0-05-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 users vboxusers 
wireshark
+ _MarkForUpload: True

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

Title:
  Ryzen5 2500U Vega 8 raven ridge flickering screen

Status in linux package in Ubuntu:
  New

Bug description:
  Hey,

  I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR.
  My display is flickering, depending on the displayed content in different 
frequency.

  Video of the symptom: 
https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-09 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.0-05-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 users vboxusers 
wireshark
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip

[Seth Forshee]

Looks like something going wrong with the floppy driver. From the
description this sounds like a race. I note that a bug with essentially
the same stack trace was fixed in 4.20, de7b75d82f70 "floppy: fix race
condition in __floppy_read_block_0()." We have that fix though, so not
sure what is causing it here.

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

Title:
  mdadm, mkfs, other io commands hang, stuck task, bad rip

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  1. disco
  2. # apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 5.0.0.13.14
Candidate: 5.0.0.13.14
Version table:
   *** 5.0.0.13.14 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  3. installation completes sucessfully
  4. Running an installation of Disco creating filesystems and probing things 
will hang (stuck task) every so often.  When it happens, the kernel throws an 
oops and bad rip value.

  [  967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds.
  [  967.811787]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.815500] mdadm   D0 12213  12207 0x
  [  967.815503] Call Trace:
  [  967.815509]  __schedule+0x2d0/0x840
  [  967.815511]  ? __switch_to_asm+0x40/0x70
  [  967.815512]  ? __switch_to_asm+0x34/0x70
  [  967.815514]  schedule+0x2c/0x70
  [  967.815516]  schedule_preempt_disabled+0xe/0x10
  [  967.815518]  __mutex_lock.isra.10+0x2e4/0x4c0
  [  967.815522]  ? exact_lock+0x11/0x20
  [  967.815524]  __mutex_lock_slowpath+0x13/0x20
  [  967.815528]  mutex_lock+0x2c/0x30
  [  967.815530]  __blkdev_get+0x7b/0x550
  [  967.815532]  ? bd_acquire+0xd0/0xd0
  [  967.815533]  blkdev_get+0x10c/0x330
  [  967.815535]  ? bd_acquire+0xd0/0xd0
  [  967.815537]  blkdev_open+0x92/0x100
  [  967.815539]  do_dentry_open+0x143/0x3a0
  [  967.815540]  vfs_open+0x2d/0x30
  [  967.815542]  path_openat+0x2d4/0x16d0
  [  967.815547]  ? put_device+0x17/0x20
  [  967.815552]  ? scsi_device_put+0x2b/0x30
  [  967.815553]  do_filp_open+0x93/0x100
  [  967.81]  ? strncpy_from_user+0x56/0x1b0
  [  967.815558]  ? __alloc_fd+0x46/0x140
  [  967.815560]  do_sys_open+0x177/0x280
  [  967.815561]  ? _cond_resched+0x19/0x30
  [  967.815563]  __x64_sys_openat+0x20/0x30
  [  967.815566]  do_syscall_64+0x5a/0x110
  [  967.815567]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.815568] RIP: 0033:0x7faa36406cce
  [  967.815572] Code: Bad RIP value.
  [  967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 
0101
  [  967.815574] RAX: ffda RBX: 4000 RCX: 
7faa36406cce
  [  967.815575] RDX: 4000 RSI: 564df70257b0 RDI: 
ff9c
  [  967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: 

  [  967.815576] R10:  R11: 0246 R12: 
7ffedb664240
  [  967.815577] R13:  R14: 0001 R15: 
564df7023e00

  [  967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds.
  [  967.803509]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.810235] mkfs.btrfs  D0  3767   1866 0x
  [  967.810239] Call Trace:
  [  967.810251]  __schedule+0x2d0/0x840
  [  967.810254]  ? __switch_to_asm+0x34/0x70
  [  967.810256]  ? __switch_to_asm+0x40/0x70
  [  967.810258]  schedule+0x2c/0x70
  [  967.810260]  schedule_timeout+0x258/0x360
  [  967.810277]  wait_for_completion+0xb7/0x140
  [  967.810281]  ? wake_up_q+0x80/0x80
  [  967.810293]  __floppy_read_block_0+0x138/0x190 [floppy]
  [  967.810298]  ? floppy_cmos_show+0x30/0x30 [floppy]
  [  967.810302]  floppy_revalidate+0xf8/0x230 [floppy]
  [  967.810307]  check_disk_change+0x62/0x70
  [  967.810309]  floppy_open+0x2ae/0x380 [floppy]
  [  967.810311]  __blkdev_get+0xe5/0x550
  [  967.810313]  ? bd_acquire+0xd0/0xd0
  [  967.810315]  blkdev_get+0x10c/0x330
  [  967.810316]  ? bd_acquire+0xd0/0xd0
  [  967.810318]  blkdev_open+0x92/0x100
  [  967.810321]  do_dentry_open+0x143/0x3a0
  [  967.810323]  vfs_open+0x2d/0x30
  [  967.810326]  path_openat+0x2d4/0x16d0
  [  967.810328]  ? filename_lookup.part.60+0xe0/0x170
  [  967.810332]  ? strncpy_from_user+0x56/0x1b0
  [  967.810333]  do_filp_open+0x93/0x100
  [  967.810353]  ? strncpy_from_user+0x56/0x1b0
  [  967.810358]  ? __alloc_fd+0x46/0x140
  [  967.810360]  do_sys_open+0x177/0x280
  [  967.810362]  ? _cond_resched+0x19/0x30
  [  967.810364]  __x64_sys_openat+0x20/0x30
  [  967.810368]  do_syscall_64+0x5a/0x110
  [  967.810369]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.810372] RIP: 0033:0x7f46b99374db
  [ 

[Kernel-packages] [Bug 1825554] ProcEnviron.txt

[Lukas Wiest]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1825554/+attachment/5257100/+files/ProcEnviron.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/1825554

Title:
  Ryzen5 2500U Vega 8 raven ridge flickering screen

Status in linux package in Ubuntu:
  New

Bug description:
  Hey,

  I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR.
  My display is flickering, depending on the displayed content in different 
frequency.

  Video of the symptom: 
https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-09 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.0-05-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 users vboxusers 
wireshark
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1825554] ProcCpuinfoMinimal.txt

[Lukas Wiest]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1825554/+attachment/5257099/+files/ProcCpuinfoMinimal.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/1825554

Title:
  Ryzen5 2500U Vega 8 raven ridge flickering screen

Status in linux package in Ubuntu:
  New

Bug description:
  Hey,

  I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR.
  My display is flickering, depending on the displayed content in different 
frequency.

  Video of the symptom: 
https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-09 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.0-05-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 users vboxusers 
wireshark
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1825554] Missing required logs.

[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 1825554

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

Title:
  Ryzen5 2500U Vega 8 raven ridge flickering screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hey,

  I'm running Ubuntu 18.10 on a Lenovo Yoga 530 14-AHR.
  My display is flickering, depending on the displayed content in different 
frequency.

  Video of the symptom: 
https://www.dropbox.com/s/ulbqo7taspx60vv/VID_20190123_151449.mp4?dl=0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-09 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 5.0.0-05-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 users vboxusers 
wireshark
  _MarkForUpload: True

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

-- 
Mailing list: https://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 1822581] [NEW] HP 1030 G3 fn-keys not working

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key 
combinations are only working partially. 
What works: Volume up/down/mute, Airplane mode
What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights

I already tried solutions regarding editing the Kernel Parameter
acpi_osi in the grub config but can not get the keys to work. In case of
screen brightness changing it using the desktop slider works.

But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
Running showkey -k results in a keycode 465 pressed and released event for all 
three key combinations.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: udev 239-7ubuntu10.10
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
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.core.rules
Date: Mon Apr  1 14:22:47 2019
InstallationDate: Installed on 2019-03-30 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: HP HP EliteBook x360 1030 G3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2019
dmi.bios.vendor: HP
dmi.bios.version: Q90 Ver. 01.06.00
dmi.board.name: 8438
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.38.00
dmi.chassis.asset.tag: 5CD8427YK5
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
dmi.product.family: 103C_5336AN HP EliteBook x360
dmi.product.name: HP EliteBook x360 1030 G3
dmi.product.sku: 4QZ13ES#ABD
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug cosmic
-- 
HP 1030 G3 fn-keys not working
https://bugs.launchpad.net/bugs/1822581
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working

[Marcel Munce]

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

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  New

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  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
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1822581] Status changed to Confirmed

[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/1822581

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  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
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked

[Connor Kuehl]

** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  Lenovo ideapad 330-15ICH Wifi rfkill hard blocked

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  === SRU Justification ===

  [Impact]
  Lenovo ideapad 330-15ICH 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 ===

  The issue here is that the drivers/platform/x86/ideapad_laptop.c
  module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill
  switch, reads the I/O port for its state, gets a zero, and therefore
  reports to the kernel that RFkill is hard-blocked.

  The current workaround is to blacklist the module to stop it being
  loaded.

  I've attached a simple patch for the module that teaches it that this
  model does not have a hardware RF kill switch.

   Original Report -

  Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165
  card, specifically on a Lenovo ideapad 330 laptop.

  A current workaround:

  - Blacklist the "ideapad-laptop" module.
  - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or 
something similar (if it does not already exist), and append "blacklist 
ideapad-laptop" to the file. Save and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dustin 1948 F pulseaudio
   /dev/snd/pcmC0D0p:   dustin 1948 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 15 04:08:20 2019
  InstallationDate: Installed on 2019-01-15 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210e Acer, Inc
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 3938:1047
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81FK
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 
2012" quiet splash nouveau.modeset=0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7ZCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15ICH
  dmi.modalias: 
dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH:
  dmi.product.family: ideapad 330-15ICH
  dmi.product.name: 81FK
  dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH
  dmi.product.version: Lenovo ideapad 330-15ICH
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1806681] Re: hp_wmi: query 0xd returned error 0x5

[Marcel Munce]

Possibility that this error results in some hotkey combinations (brightness 
up/down) not working?
The corresponding combinations create no scan code. 
And hence there not handled by ACPI maybe it's related to the hp_wmi module?

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

Title:
  hp_wmi: query 0xd returned error 0x5

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

Bug description:
  Hello,

  dmesg:
  [   18.296366] hp_wmi: query 0xd returned error 0x5

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:05:38 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1822581] Re: HP 1030 G3 fn-keys not working

[Marcel Munce]

Running scancode -s showed, that there is no scancode passed for those
combinations.

Maybe this correlates with errors produced by the hp_wmi module
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758442)

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

Title:
  HP 1030 G3 fn-keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  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
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

[Connor Kuehl]

Hi all!

The Bionic and Cosmic kernels containing a fix for this issue are now in
their "-proposed" repositories. Could someone please verify if they fix
the issue you're experiencing?

For those reading that haven't done this before, here are instructions
for enabling and using the "-proposed" repository:
https://wiki.ubuntu.com/Testing/EnableProposed

Thank you!

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

Title:
  Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
  (0x0f)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in Fedora:
  New

Bug description:
  === SRU Justification ===
  [Impact]
  Kernel constantly reports "Bluetooth: hci0: last event is not cmd
  complete (0x0f)" when using Bluetooth.

  [Fix]
  If the HCI event is Command Status, just bail because there's no further
  thing to do.

  [Test]
  Open Gnome Control Center's Bluetooth panel to start BT scan. The kernel
  keeps spewing out the messege.
  After applying the patch the message doesn't show anymore.

  [Regression Potential]
  Low. Upstream patch and succesfully tested.

  
  === Original Bug Report ===

  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

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

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

-- 
Mailing list: https://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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

Tested bionic-hwe - the issue does not occur with 2048 MiB.

The closest issue filed upstream I found is this:
https://bugzilla.kernel.org/show_bug.cgi?id=199845

** Bug watch added: Linux Kernel Bug Tracker #199845
   https://bugzilla.kernel.org/show_bug.cgi?id=199845

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

-- 
Mailing list: https://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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

** Changed in: qemu (Ubuntu)
   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/1797581

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

-- 
Mailing list: https://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 1813651] Re: hpsa: DMAR invalid read

[Terry Rudd]

Guilherme, is there going to be further work on this bug?

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

Title:
  hpsa: DMAR invalid read

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  Recently in kernel 4.20-rc1 and newer we observed the following
  spontaneous issue with hpsa when intel_iommu is enabled:

  [ 5173.952022] DMAR: DRHD: handling fault status reg 2
  [ 5174.190649] DMAR: [DMA Read] Request device [03:00.0] fault addr eefdd000 
[fault reason 06] PTE Read access is not set

  There's a commit that touches DMA in hpsa: "scsi: hpsa: switch to generic DMA 
API"
  We've tested with this commit reverted on top of 4.20-rc1 and it reproduces 
(the trigger is a kernel build). We cannot reproduce in 4.19.

  Investigation is ongoing.

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

-- 
Mailing list: https://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

[Sean Feole]

** Tags added: regression-testing-passed

-- 
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:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: Signoff
  phase-changed: Thursday, 18. April 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Fix Released
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 Bionic:
  Confirmed

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: Signoff
  phase-changed: Wednesday, 17. April 2019 17:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1822810/+subscriptions

-- 
Mailing list: https://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

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822812
  phase: Signoff
  phase-changed: Thursday, 18. April 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   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-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:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: Signoff
  phase-changed: Thursday, 18. April 2019 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   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
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Signoff
  phase-changed: Wednesday, 17. April 2019 17:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1822810

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Fix Released
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 Bionic:
  Confirmed

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: Signoff
  phase-changed: Wednesday, 17. April 2019 17:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1822810/+subscriptions

-- 
Mailing list: https://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 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

Just tried Ubuntu 19 today and the problem persists (can't even install
ubuntu because it gives io error)

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

Hi Kai-Heng Feng, do you have any news on this problem? It'd be great to
know.

Than you so much!

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic

[Kernel-packages] [Bug 1820948] Re: i40e xps management broken when > 64 queues/cpus

[Connor Kuehl]

Hi Nivedita,

The Bionic kernel containing a fix for this issue is now in the
"-proposed" repository. Could you (or the external reporter mentioned
earlier in the ticket) try the proposed kernel to see if it fixes the
issue?

Also, I saw you left a note earlier saying that you were still
investigating this for Xenial; are there any updates from that
investigation?

Thank you!

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

Title:
  i40e xps management broken when > 64 queues/cpus

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

Bug description:
  [Impact]
  Transmit packet steering (xps) settings don't work when
  the number of queues (cpus) is higher than 64. This is
  currently still an issue on the 4.15 kernel (Xenial -hwe
  and Bionic kernels).

  It was fixed in Intel's i40e driver version 2.7.11 and
  in 4.16-rc1 mainline Linux (i.e. Cosmic, Disco have fix).

  Fix
  -
  The following commit fixes this issue (as identified
  by Lihong Yang in discussion with Intel i40e team):

  "i40e: Fix the number of queues available to be mapped for use"
  Commit: bc6d33c8d93f520e97a8c6330b8910053d4f

  It requires the following commit as well:

  i40e: Do not allow use more TC queue pairs than MSI-X vectors exist
  Commit:   1563f2d2e01242f05dd523ffd56fe104bc1afd58

  
  [Test Case]
  1. Kernel version: Bionic/Xenial -hwe: any 4.15 kernel
     i40e driver version: 2.1.14-k
     Any system with > 64 CPUs

  2. For any queue 0 - 63, you can read/set tx xps:

  echo  > /sys/class/net/eth2/queues/tx-63/xps_cpus
  echo $?
  0
  cat /sys/class/net/eth2/queues/tx-63/xps_cpus
  00,,

    But for any queue number > 63, we see this error:

  echo  > /sys/class/net/eth2/queues/tx-64/xps_cpus
  echo: write error: Invalid argument

  cat /sys/class/net/eth2/queues/tx-64/xps_cpus
  cat: /sys/class/net/eth2/queues/tx-64/xps_cpus: Invalid argument

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

-- 
Mailing list: https://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 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

[Emrah ÖZCAN]

** Summary changed:

- Acer Aspire Travelmate 535 after opening lid black screen and freeze occurs
+ Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

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

Title:
  Acer Aspire Travelmate 5335 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04
  i386 32 bit processor

  On settings "do anything when closing lid" is aplied.
  Hard reset needs .

  Tried all other ways.

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

-- 
Mailing list: https://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 1746340] Re: Samsung SSD corruption (fsck needed)

[Fabian]

Hi,

a little update from my side: It seems that faulty memory was the reason
for the data corruptions in my case. I have replaced the memory module
and everything seems to work fine now. I was quite surprised though that
the memory was defective since I did test it carefully for many hours
with memtest (20+ passes without any errors). The errors only occured
when running Ubuntu ...

The memory was the only thing I have changed, so I am very sure that
this was the cause ...

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz   

[Kernel-packages] [Bug 1818617] Re: [amdgpu] screen corruption when using touchpad

[Connor Kuehl]

Hello all,

A Bionic kernel containing a fix for this issue is in "-proposed". If
that kernel fixes the issue described here please let us know.

For those reading that haven't done this before, here are instructions
for enabling and using the "-proposed" repository:
https://wiki.ubuntu.com/Testing/EnableProposed

Thank you!

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

Title:
  [amdgpu] screen corruption when using touchpad

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  An OEM system is suffering from screen corruption when the touchpad is used. 
This would be fixed by backporting these commits from 4.18:

  ebdef28ebbcf767 drm/amdgpu/gmc: steal the appropriate amount of vram for fw 
hand-over (v3)
  6f752ec2c20c6a5 drm/amdgpu: Free VGA stolen memory as soon as possible.

  [Test case]
  boot a fixed kernel on the affected system, check that it doesn't suffer from 
the corruption

  [Regression potential]
  low, this has been upstream since 4.18, and AMD asked us to backport these

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

-- 
Mailing list: https://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 1821961] Re: Fix for dual Intel NVMes

[Connor Kuehl]

Hello all,

A Bionic kernel containing a fix for this issue is in "-proposed". If
that kernel fixes the issue described here please let us know.

For those reading that haven't done this before, here are instructions
for enabling and using the "-proposed" repository:
https://wiki.ubuntu.com/Testing/EnableProposed

Thank you!

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

Title:
  Fix for dual Intel NVMes

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

Bug description:
  [Impact]
  SRU for LP: #1811755 doesn't really fix the issue. Only one of the two NVMe 
can be correctly enumerated.

  [Fix]
  There are two separate entries for the Intel NVMe device. Fix that.

  [Test]
  User confirms it works.

  [Regression Potential]
  The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been
  verified by the bug reporter.

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

-- 
Mailing list: https://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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[d.slepic...@gmail.com]

Have the same problem. Ubuntu 18.04 LTS

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in console-setup source package in Cosmic:
  New
Status in linux source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  New
Status in console-setup source package in Disco:
  In Progress
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  New
Status in linux source package in Eoan:
  New
Status in xorg-server source package in Eoan:
  New

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

-- 
Mailing list: https://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 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10

[Andrea Righi]

Update: the patch to downgrade the error "Unable to open file..." to a
warning seems to be already applied to the bionic kernel
(https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-
next&id=58441dc86d7b066a2c02079829a96035587a7066) and the cosmic kernel
(https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/cosmic/commit/?h=master-
next&id=ed79083b0d87cef2a64f906614f49faa40337e96).

About the other "uevent" errors, do you think it would help to provide a
test kernel with some little extra instrumentation to track down the
userspace task that is (apparently) sending incorrect data via sysfs
(i.e., adding pid, name, etc. to the error message)?

-- 
You 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/ct

[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10

[Manoj Iyer]

Fresh install of 18.04 on Power9 system, installed linux-image-generic-
hwe-18.04

ubuntu@bobone:~$ uname -a 
Linux bobone 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 
2019 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@bobone:~$

ubuntu@bobone:~$ dmesg -xT -l emerg,alert,crit,err
kern  :err   : [Fri Apr 19 21:12:08 2019] integrity: Unable to open file: 
/etc/keys/x509_ima.der (-2)
kern  :err   : [Fri Apr 19 21:12:08 2019] integrity: Unable to open file: 
/etc/keys/x509_evm.der (-2)
kern  :err   : [Fri Apr 19 21:12:08 2019] vio vio: uevent: failed to send 
synthetic uevent
kern  :err   : [Fri Apr 19 21:12:14 2019] vio vio: uevent: failed to send 
synthetic uevent
ubuntu@bobone:~$

Looks like the "integrity: Unable to open file" are still reported as
"kern: err" rather than warnings like the patch
(https://lists.ubuntu.com/archives/kernel-
team/2017-February/082526.html) was supposed to. And, looks like the
"vio vio: uevent:" error occurs only on boot, and does not seem to
appear when the system is running.

Looks like /etc/keys/x509-blah is missing in initramfs? May be because
the feature is not supported? But seems like the right thing to do is to
downgrade the err to warn.

buntu@bobone:~$ dmesg | grep ima
[0.00] PCI host bridge /pciex@600c3c000 (primary) ranges:
[2.379848] ima: Allocated hash algorithm: sha256
[2.518823] evm: security.ima
[2.618501] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
ubuntu@bobone:~$

ubuntu@bobone:~$ dmesg | grep evm
[2.518625] evm: Initialising EVM extended attributes:
[2.518651] evm: security.selinux
[2.518676] evm: security.SMACK64
[2.518691] evm: security.SMACK64EXEC
[2.518716] evm: security.SMACK64TRANSMUTE
[2.518740] evm: security.SMACK64MMAP
[2.518773] evm: security.apparmor
[2.518823] evm: security.ima
[2.518855] evm: security.capability
[2.518878] evm: HMAC attrs: 0x1
[2.618504] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
ubuntu@bobone:~$ 

Reference: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908

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

[Kernel-packages] [Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

[Michael Aaron Murphy]

This still occurs in 19.04 with nvidia-driver-418.

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ideapad 510-15IKB
  OS: Ubuntu 18.04 bionic
  Kernel: x86_64 Linux 4.15.0-20-generic
  DE: GNOME
  CPU: Intel Core i5-7200U @ 4x 3.1GHz
  GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus)
  UEFI boot, Secure Boot disabled.

  I installed the proprietary graphics driver with Software Properties and 
Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, 
Dolphin) were working fine.
  To get rid of tearing I added nvidia-drm.modeset=1 to 
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && 
update-initramfs -u and rebooted.
  After doing that, Vulkan applications stopped working because they couldn't 
initialize the Vulkan swap chain until I reverted the changes to GRUB.

  Everything works as expected if lightdm is used instead of gdm3.

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

-- 
Mailing list: https://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 1814440] Re: [QCA9565 / AR9565] Bluetooth switches off automatically

[Launchpad Bug Tracker]

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [QCA9565 / AR9565] Bluetooth switches off automatically

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Buetooth will switch automatically when i try to connect to my
  speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  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.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  3 14:13:24 2019
  InstallationDate: Installed on 2019-01-09 (24 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80J2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=215a5782-5ca0-46f3-9fcf-f3a8c1e344db ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo E50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900056 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo E50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvr31900056WIN:cvnLENOVO:ct10:cvrLenovoE50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80J2
  dmi.product.version: Lenovo E50-80
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: B8:86:87:44:55:70  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN ISCAN 
RX bytes:748 acl:0 sco:0 events:59 errors:0
TX bytes:4892 acl:0 sco:0 commands:59 errors:0

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

-- 
Mailing list: https://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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[drs305]

Same error message for me. Unable to boot into the 4 kernel backup as
well. Repeatedly boots to the login screen, which shows my name but
refuses to accept my password.

Attempted installation with the beta and now the released version with
same result.

Running standard Ubuntu 18.10 - at least I was until the new upgrade
failed...

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions

-- 
Mailing list: https://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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions

-- 
Mailing list: https://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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions

-- 
Mailing list: https://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 1799019] Re: Linux crashed so severly that I have to reinstall.

[Robert Pearson]

That is not the only bug that has “slip through our radar”. The latest
update of Ubuntu MATE lies about the owner of files both in the command
line ls -l command and the Caja Properties window. Both claim the owner is
root. Since I am logged on a robert not root I would not be able to create,
modify, or delete any files in my system (ls always says to owner is root).
Since I can make changes then either the file system permissions code is
broken or the owner is being incorrectly reported.

I reported this problem about 4 weeks ago. It has “slip through our radar”.
No response from anybody despite the fact that this is a security problem
in the basic kernel.

Robert

On Fri, Apr 19, 2019 at 7:50 AM Po-Hsu Lin 
wrote:

> Hello,
> my apology for this situation, we let this package (linux-signed) slip
> through our radar in the old days. The process has been improved now.
>
> I am gonna close this bug with Invalid, but please feel free to open a
> new bug with command "ubuntu-bug linux" base on what you have
> encountered recently (preferably one issue in a report, and with a
> supported version, as Ubuntu Mate 14.10 has already reaches it End-of-
> Life [1]).
>
> Or ask questions on community forums like https://askubuntu.com
> https://ubuntuforums.org/
>
> Thank you.
>
> [1] https://en.wikipedia.org/wiki/Ubuntu_MATE
>
> ** Changed in: linux-signed (Ubuntu)
>Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799019
>
> Title:
>   Linux crashed so severly that I have to reinstall.
>
> Status in linux-signed package in Ubuntu:
>   Invalid
>
> Bug description:
>   First Google Chrome and Chromium crashed closing all their windows.
>   Then most, but not all, of the VisualWorks windows diappeared.
>   (Unfortunately the System window closed so I could not exit properly).
>   Then the list of open windows at the bottom of the screen disappeared,
>   as did the menu bar at the top. With no menu to shutdown, I had to
>   turn power off.
>
>   When I tried to reboot I got the Ubuntu symbol and the progress dots
>   underneath. After more than an hour, I got a command line to log in.
>   (Not a terminal window - Ubuntu never started.)
>
>   I was able to log in but could do nothing since this was a system
>   without MATE or any window GUI.
>
>   Every time I try to reboot, I get the save progress dots for over an
>   hour and then the terminal mode login prompt.
>
>   I had to boot from the distribution DVD to make this report before re-
>   installing the system.
>
>   Please fix your documentation on reporting system crashes. What is
>   "apport" and how do I run it?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-20-generic 4.15.0-20.21
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CasperVersion: 1.394
>   CurrentDesktop: MATE
>   Date: Sun Oct 21 02:13:33 2018
>   LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: linux-signed
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1799019/+subscriptions
>

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

Title:
  Linux crashed so severly that I have to reinstall.

Status in linux-signed package in Ubuntu:
  Invalid

Bug description:
  First Google Chrome and Chromium crashed closing all their windows.
  Then most, but not all, of the VisualWorks windows diappeared.
  (Unfortunately the System window closed so I could not exit properly).
  Then the list of open windows at the bottom of the screen disappeared,
  as did the menu bar at the top. With no menu to shutdown, I had to
  turn power off.

  When I tried to reboot I got the Ubuntu symbol and the progress dots
  underneath. After more than an hour, I got a command line to log in.
  (Not a terminal window - Ubuntu never started.)

  I was able to log in but could do nothing since this was a system
  without MATE or any window GUI.

  Every time I try to reboot, I get the save progress dots for over an
  hour and then the terminal mode login prompt.

  I had to boot from the distribution DVD to make this report before re-
  installing the system.

  Please fix your documentation on reporting system crashes. What is
  "apport" and how do I run it?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0

[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10

[Andrea Righi]

@manjo thanks for testing again! Now I see, we need to apply another
small patch to security/integrity/digsig.c, that seems to have exactly
the same error message that should be considered a warning instead. I'll
post a fix soon.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 @ 
(NF

[Kernel-packages] [Bug 982299] Re: [Dell Inspiron 1520] Screen stays black after laptop lid is opened

[Christopher M. Penalver]

** This bug is no longer a duplicate of bug 1825219
   Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

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

Title:
  [Dell Inspiron 1520] Screen stays black after laptop lid is opened

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

Bug description:
  Every time I close my laptop's lid and wait for few minutes -- screen stays 
black.
  I can switch to text console (Alt-Ctrl-F1) and back to black X screen 
(Alt-Ctrl-F7). I can login in console.
  I don't see mouse cursor on X screen.
  I'm using free nouveau drivers.

  This issue appeared just after I've upgraded to 12.04 beta2.

  I'm running 'sudo restart lightdm' from console to bring X to life.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sun Apr 15 16:35:07 2012
  DistUpgraded: 2012-03-30 06:52:10,270 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/gnome/defaults.list'
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: Dell Inc. Inspiron 1520
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to precise on 2012-03-30 (16 days ago)
  dmi.bios.date: 07/11/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0UW306
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0UW306:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu35
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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