date:20180702

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 1779802

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

Title:
  Touchpad of ThinkPad P52 failed to work with message "lost sync at
  byte"

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New

Bug description:
  On ThinkPad P52:
  touchpad failed to work and reports:
  [ 2.713396] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input8
  [ 2.725328] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

  And lots of errors printed out:

  [ 19.468387] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.474455] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.480657] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.487665] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494682] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494685] psmouse serio1: issuing reconnect request
  [ 19.679895] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.686285] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.692642] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.699858] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.706873] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6

  And the middle button can not work too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1779802/+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 1779802] Re: Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"

2018-07-02 Thread Shengyao Xue

** No longer affects: linux

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

Title:
  Touchpad of ThinkPad P52 failed to work with message "lost sync at
  byte"

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New

Bug description:
  On ThinkPad P52:
  touchpad failed to work and reports:
  [ 2.713396] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input8
  [ 2.725328] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

  And lots of errors printed out:

  [ 19.468387] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.474455] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.480657] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.487665] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494682] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494685] psmouse serio1: issuing reconnect request
  [ 19.679895] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.686285] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.692642] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.699858] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.706873] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6

  And the middle button can not work too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1779802/+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 1779802] Re: Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"

2018-07-02 Thread AaronMa

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

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

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

Title:
  Touchpad of ThinkPad P52 failed to work with message "lost sync at
  byte"

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New

Bug description:
  On ThinkPad P52:
  touchpad failed to work and reports:
  [ 2.713396] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input8
  [ 2.725328] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

  And lots of errors printed out:

  [ 19.468387] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.474455] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.480657] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.487665] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494682] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494685] psmouse serio1: issuing reconnect request
  [ 19.679895] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.686285] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.692642] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.699858] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.706873] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6

  And the middle button can not work too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1779802/+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 1779802] Re: Touchpad of ThinkPad P52 failed to work with message "lost sync at byte"

2018-07-02 Thread AaronMa

** Tags added: originate-from-1752778

** Tags added: sutton

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

Title:
  Touchpad of ThinkPad P52 failed to work with message "lost sync at
  byte"

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New

Bug description:
  On ThinkPad P52:
  touchpad failed to work and reports:
  [ 2.713396] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input8
  [ 2.725328] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

  And lots of errors printed out:

  [ 19.468387] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.474455] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.480657] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.487665] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494682] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.494685] psmouse serio1: issuing reconnect request
  [ 19.679895] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.686285] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.692642] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.699858] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 19.706873] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6

  And the middle button can not work too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1779802/+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 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

2018-07-02 Thread Khaled El Mously

Proposed fix for lp #1771764 and lp #1771783

Please ignore the first proposal.

** Patch added: "proposed-fix-1771764-1771783.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+attachment/5159000/+files/proposed-fix-1771764-1771783.debdiff

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial

2018-07-02 Thread Khaled El Mously

Proposed fix for lp #1771764 and lp #1771783

** Patch added: "proposed-fix-1771764-1771783.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+attachment/5158998/+files/proposed-fix-1771764-1771783.debdiff

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

Title:
  iproute2: unable to add ip lwt mpls route on xenial

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  The following command does not work:

  $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
  Error: "nexthop" or end of line is expected instead of "encap"

  In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
  $ ip -V
  ip utility, iproute2-ss151103

  =>
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

  With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
  $ modprobe mpls_iptunnel
  $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
  $ ./ip/ip r
  [snip]
  10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

  At least, this patch is missing:
  1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+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 1764286] Re: Boot freeze due to Nvidia Geforce GTX 950M

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

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

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

Title:
  Boot freeze due to Nvidia Geforce GTX 950M

Status in linux package in Ubuntu:
  Expired

Bug description:
  When running Ubuntu 17.10 on my laptop which has a "Nvidia Geforce GTX
  950M" and a "Intel HD Graphics 530" graphic card, the boot process
  freezes.

  The cause is that the current Linux kernel does not include FOSS drivers for 
"Nvidia Geforce GTX 950M".
  The solution to avoid that freeze is to add the "nomodeset" grub boot 
parameter or to install the proprietary Nvidia driver.

  My concern is that you have to be aware of that circumvent when installing 
Ubuntu OS for the first time.
  I think that it would be more logical that the Linux kernel uses the low 
performance graphic card "Intel HD Graphics 530" by default, without trying to 
use "Nvidia Geforce GTX 950M" which is not natively supported.
  That would avoid the bad experience of boot freeze at first meeting.


  Computer :
  Model = Asus N752VX-GC164T
  Ubuntu 17.10
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   user   1861 F...m pulseaudio
   /dev/snd/controlC0:  user   1861 F pulseaudio
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-13 (92 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0461:4d22 Primax Electronics, Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N752VX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=5b9acdb6-aa5b-4801-8cd6-40621a2028d4 ro nouveau.modeset=0
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  artful
  Uname: Linux 4.13.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N752VX.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N752VX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN752VX.301:bd08/18/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N752VX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+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 1759354] Re: 18.04 After suspend fan goes to max speed on resume, have to reset in bios

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

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

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

Title:
  18.04 After suspend fan goes to max speed on resume, have to reset in
  bios

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed 18.04 on my Thinkpad X260. When I closed the lid it
  suspended. Opened the lid and the fan went to maximum. I shut down and
  booted into Windows 10 (dual boot machine) and the fan was still at
  maximum. I had to reset BIOS to defaults, so it looks like Ubuntu is
  still messing up the BIOS settings, at least on the X260.

  Ubuntu is up to date as of 2018/03/27.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759354/+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 1766624] Re: AArch64 kernel panic on APM Mustang

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

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

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

Title:
  AArch64 kernel panic on APM Mustang

Status in linux package in Ubuntu:
  Expired

Bug description:
  Random kernel panic on AArch64 APM Mustang running ubuntu xenial kernel.  
  ==
  [2244826.215921] Unhandled fault: alignment fault (0x9621) at 
0x03b00a53
  [2244826.223377] Internal error: : 9621 [#1] SMP
  [2244826.228057] Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc overlay shpchp 
xgene_edac edac_core xhci_plat_hcd xgene_rng uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd grace ib_iser sunrpc rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear realtek ahci_xgene 
libahci_platform xgene_enet libahci mdio_xgene aes_neon_blk ablk_helper cryptd
  [2244826.293934] CPU: 3 PID: 7232 Comm: basename Not tainted 
4.4.0-101-generic #124-Ubuntu
  [2244826.301896] Hardware name: AppliedMicro Mustang/Mustang, BIOS 1.1.0 Apr 
22 2015
  [2244826.309339] task: 800119bf6800 ti: 80013ec74000 task.ti: 
80013ec74000
  [2244826.316960] PC is at _raw_spin_lock_irqsave+0x24/0x60
  [2244826.322158] LR is at try_to_wake_up+0x44/0x3a8
  [2244826.326750] pc : [] lr : [] pstate: 
61c5
  [2244826.334279] sp : 80013ec77b40
  [2244826.337746] x29: 80013ec77b40 x28: 0075 
  [2244826.343224] x27: 80001c1d3b80 x26: 800166d75a70 
  [2244826.348698] x25: 8000fad8c190 x24: 800166d75a80 
  [2244826.354175] x23:  x22: 0003 
  [2244826.359652] x21: 03b00a53 x20:  
  [2244826.365128] x19: 03b00a53 x18:  
  [2244826.370603] x17:  x16: 80210960 
  [2244826.376079] x15:  x14:  
  [2244826.381553] x13:  x12:  
  [2244826.387029] x11: 8003e9a36700 x10: 00d6 
  [2244826.392504] x9 : 8093fee8 x8 :  
  [2244826.397978] x7 : 8000fad8ccf8 x6 : 8000fad8c258 
  [2244826.403452] x5 :  x4 : 0001 
  [2244826.408927] x3 :  x2 :  
  [2244826.414402] x1 : 0003 x0 : 01c0 

  [2244826.421531] Process basename (pid: 7232, stack limit = 
0x80013ec74020)
  [2244826.428543] Stack: (0x80013ec77b40 to 0x80013ec78000)
  [2244826.434432] 7b40: 80013ec77b60 800f28b4 03b003af 
8003ee0c4000
  [2244826.442393] 7b60: 80013ec77bc0 800f2c40 03b003af 
0001
  [2244826.450355] 7b80: 800166d75a70 800166d75a68 800166d75a70 
800166d75a80
  [2244826.458316] 7ba0: 8000fad8c190 800166d75a70 80001c1d3b80 
0075
  [2244826.466276] 7bc0: 80013ec77be0 8011433c 03b003af 
8090ed94
  [2244826.474237] 7be0: 80013ec77c20 8090ef30 800166d75a68 
0001
  [2244826.482199] 7c00: 80db2000  800166d75a40 
8020b790
  [2244826.490159] 7c20: 80013ec77cb0 8090e320 800166d75a68 

  [2244826.498121] 7c40: 8000fad8cd48  800166d75a40 

  [2244826.506082] 7c60: 8000fad8c190 800166d75a60 80001c1d3b80 
8000fad8ccb0
  [2244826.514044] 7c80: 8000fad8c960 800143927b68 800143927c88 
800119bf6800
  [2244826.522006] 7ca0: 8001 cb88537fdc8ba65f 80013ec77cd0 
8020c640
  [2244826.529966] 7cc0: 8000fad8cc80  80013ec77d70 
8020ccb8
  [2244826.537927] 7ce0: 8000fad8c190 8000fad8cc80  
f7517000
  [2244826.545889] 7d00: 80eb4000  80001c1d3b80 
80013ec77eb0
  [2244826.553850] 7d20: 0010 0075 80eb4000 

  [2244826.561812] 7d40: 1c1d3b80 00d6 8003e9a36700 
f7507000
  [2244826.569774] 7d60:  f7517000 80013ec77db0 
8020e104
  [2244826.577736] 7d80: 80001c1d3b80 8000fad8cc80 f7517000 

  [2244826.585696] 7da0: f7507000 f7517000 80013ec77df0 
80210920
  [2244826.593657] 7dc0: 8000fad8cc80  0070 

  [2244826.601617]

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

2018-07-02 Thread Kai-Heng Feng

Can you attach the error? Maybe use something else like virtual box to
see if KVM is the culprit?

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

Mark,

Please log a bug of your own so we can figure that out for 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/1779476

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+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 1769610] Re: Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

2018-07-02 Thread Shrirang Bagul

@Denis,

Then the /dev/ttyS6 may now appear as /dev/ttyHSx. Can you confirm this?

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

Title:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

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

Bug description:
  Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty

  On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
  HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
  HID's INT3511/INT3512 [1].

  As a consequence, HW manufacturers have complete freedom to install any
  devices on-board as long as they can be accessed over serial tty
  interface. Once such device is Dell Edge 3002 IoT Gateway which sports
  ZigBee & GPS devices on the HS-UART ports 1 & 2 respectively.

  Post 4.15, with CONFIG_SERIAL_DEV_BUS=y, serdev port controller driver
  handles the enumeration for the slaves connected on these ports. Also,
  /dev/ttySx device nodes for these ports are no longer exposed to the
  userspace.

  This driver has been submitted upstream and is under review. This issue has
  been identified as a regression in 4.15 and multiple solutions are being
  explored. Meanwhile, to support customer and maintain release schedule,
  this driver needs to be in Ubuntu 4.15 based kernels.

  The impact is limited to systems based on Intel Atom E38XX (Baytrail-I)
  SoC's.

  More info:
  https://marc.info/?t=15245587167=1=2

  Please don't triage, this bug is for tracking purposes only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1769610/+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 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

2018-07-02 Thread Mark

I'm suffering this after this update too. It is the latest in a
depressingly long list of Ubuntu updates that have ed up my system.
You really *need* better testing of updates. If you can't improve the
testing then there needs to be a way to roll-back the system to before
an update.

Instead of the login screen I see the output of a log. Every item the
log is [ OK ] except for

[   .] A start job is running for Hold until boot process finishes
up (28s / no limit)[ OK ] Started Show Plymouth BootScreen.

The last entry is

[ OK ] Started GNOME DisplayManager. Dispatcher
Serviceupport.hanges.pp link was shut down.

lightdm is not working for me. Yes a login screen is displayed but after
login the screen goes black for quite some time then the login screen
reappears again. I am unable to use my system so this is a priority 1
bug for me.

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

This change was made by a bot.

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

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

Title:
  After putting my laptop to suspend (lid down), it does not wake up
  again

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04. After putting my laptop to suspend (lid
  down), it does not wake up again. This does not happen when I lock it
  (windows key + L) it resumes operation on keypress. This has started
  happening around 1 month ago, I am not exactly sure. This is an Asus
  K501UW

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.0-041000-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jul  2 20:22:52 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:11e0]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:11e0]
  InstallationDate: Installed on 2016-11-02 (606 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000-generic 
root=UUID=5e76175a-3add-425a-938f-e3e5c13bd41b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jul  2 20:13:27 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779704/+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 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

Thanks.

Unfortunately we are still missing some information.

Please run 'lspci -k' and send us the output. If you don't know how to
do that then just take a photo of the screen.

Please also run 'apport-collect 1779476' again. I have modified the bug
so hopefully it will give us more info the second time.

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

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+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 1779704] Re: Xorg freeze

** Tags added: suspend-resume

** Summary changed:

- Xorg freeze
+ After putting my laptop to suspend (lid down), it does not wake up again

** Package changed: xorg (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/1779704

Title:
  After putting my laptop to suspend (lid down), it does not wake up
  again

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04. After putting my laptop to suspend (lid
  down), it does not wake up again. This does not happen when I lock it
  (windows key + L) it resumes operation on keypress. This has started
  happening around 1 month ago, I am not exactly sure. This is an Asus
  K501UW

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.0-041000-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jul  2 20:22:52 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:11e0]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:11e0]
  InstallationDate: Installed on 2016-11-02 (606 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000-generic 
root=UUID=5e76175a-3add-425a-938f-e3e5c13bd41b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jul  2 20:13:27 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779704/+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 1779704] [NEW] After putting my laptop to suspend (lid down), it does not wake up again

You have been subscribed to a public bug:

I am using Ubuntu 16.04. After putting my laptop to suspend (lid down),
it does not wake up again. This does not happen when I lock it (windows
key + L) it resumes operation on keypress. This has started happening
around 1 month ago, I am not exactly sure. This is an Asus K501UW

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.10.0-041000-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Jul  2 20:22:52 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:11e0]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:11e0]
InstallationDate: Installed on 2016-11-02 (606 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. K501UW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000-generic 
root=UUID=5e76175a-3add-425a-938f-e3e5c13bd41b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K501UW.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K501UW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K501UW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jul  2 20:13:27 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug compiz-0.9 freeze suspend-resume third-party-packages 
ubuntu xenial
-- 
After putting my laptop to suspend (lid down), it does not wake up again
https://bugs.launchpad.net/bugs/1779704
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 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

Thanks. Can you please test v4.15-rc1 to be sure?

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message

2018-07-02 Thread Adam Novak

Hello,

Thanks for putting this together. I tried to get the kernels you
built, but I'm having trouble establishing a secure (https) connection
to kernel.ubuntu.com. It looks like the server might not offer https.

Can you give me the expected hashes of the files so I can verify the
downloads?

Thanks,
-Adam

On Wed, Jun 27, 2018 at 10:34 AM, Joseph Salisbury
 wrote:
> I started a kernel bisect between v4.15.0-22 and v4.15.0-23. The kernel
> bisect will require testing of about 7-10 test kernels.
>
> I built the first test kernel, up to the following commit:
> 8eca6add0defde203282476d7969a7c13bbd7d91
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1777338
>
> Can you test that kernel and report back if it has the bug or not?  I
> will build the next test kernel based on your test results.
>
>
> Thanks in advance
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1777338
>
> Title:
>   Linux 4.15.0-23 crashes during the boot process with a "Unable to
>   handle kernel NULL pointer dereference" message
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Bionic:
>   In Progress
>
> Bug description:
>   I went to boot my computer today and it wouldn't boot.
>
>   I get an "Unable to handle kernel NULL pointer dereference" message
>   during the boot process, and, a bit after that, a message from the
>   kernel watchdog about CPU #0 being stuck. Then the boot process stops
>   completely.
>
>   I was able to boot the system by telling Grub to load 4.15.0-22, which
>   works perfectly fine, so there has been a regression.
>
>   I am running Ubuntu as a Xen dom0, if that matters. I haven't tried
>   booting the offending kernel version without Xen.
>
>   I'm not sure where, if anywhere, these messages go on disk, for
>   posting.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-23-generic 4.15.0-23.25
>   ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
>   Uname: Linux 4.15.0-22-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.9-0ubuntu7.1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jun 17 10:12:58 2018
>   InstallationDate: Installed on 2017-08-06 (314 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: linux-signed
>   UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions

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

Title:
  Linux 4.15.0-23 crashes during the boot process with a "Unable to
  handle kernel NULL pointer dereference" message

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

Bug description:
  I went to boot my computer today and it wouldn't boot.

  I get an "Unable to handle kernel NULL pointer dereference" message
  during the boot process, and, a bit after that, a message from the
  kernel watchdog about CPU #0 being stuck. Then the boot process stops
  completely.

  I was able to boot the system by telling Grub to load 4.15.0-22, which
  works perfectly fine, so there has been a regression.

  I am running Ubuntu as a Xen dom0, if that matters. I haven't tried
  booting the offending kernel version without Xen.

  I'm not sure where, if anywhere, these messages go on disk, for
  posting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 17 10:12:58 2018
  InstallationDate: Installed on 2017-08-06 (314 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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 1779777] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1779777/+attachment/5158979/+files/ProcModules.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

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

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1779777/+attachment/5158982/+files/WifiSyslog.txt

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

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

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1779777/+attachment/5158974/+files/Lsusb.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1779777/+attachment/5158973/+files/Lspci.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1779777/+attachment/5158972/+files/CurrentDmesg.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1779777/+attachment/5158980/+files/PulseList.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1779777/+attachment/5158975/+files/ProcCpuinfo.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1779777/+attachment/5158981/+files/UdevDb.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1779777/+attachment/5158971/+files/CRDA.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1779777/+attachment/5158978/+files/ProcInterrupts.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

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

apport information

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

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.157.18
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 098E121600087
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+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 1779777] Re: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

apport information

** Tags added: apport-collected xenial

** Description changed:

  bcmwl-kernel-source reinstall
  
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/
  
  depmod
  
  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  koyot  2253 F pulseaudio
+  /dev/snd/controlC0:  koyot  2253 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
+ InstallationDate: Installed on 2017-11-22 (222 days ago)
+ InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ IwConfig:
+  enp4s0no wireless extensions.
+  
+  lono wireless extensions.
+ MachineType: Hewlett-Packard HP 15 Notebook PC
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-24-generic N/A
+  linux-backports-modules-4.15.0-24-generic  N/A
+  linux-firmware 1.157.18
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blocked: yes
+   Hard blocked: no
+ Tags:  xenial
+ Uname: Linux 4.15.0-24-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 12/23/2014
+ dmi.bios.vendor: Insyde
+ dmi.bios.version: F.33
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 21F7
+ dmi.board.vendor: Hewlett-Packard
+ dmi.board.version: 52.3A
+ 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.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
+ dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
+ dmi.product.name: HP 15 Notebook PC
+ dmi.product.version: 098E121600087
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1779777/+attachment/5158970/+files/AlsaInfo.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/1779777

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koyot  2253 F pulseaudio
   /dev/snd/controlC0:  koyot  2253 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6
  InstallationDate: Installed on 2017-11-22 (222 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  RelatedPackageVersions:

[Kernel-packages] [Bug 1779761] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1779761/+attachment/5158962/+files/Lspci.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1779761/+attachment/5158967/+files/ProcModules.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1779761/+attachment/5158966/+files/ProcInterrupts.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1779761/+attachment/5158961/+files/CurrentDmesg.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1779761/+attachment/5158969/+files/WifiSyslog.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1779761/+attachment/5158968/+files/UdevDb.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1779761/+attachment/5158960/+files/CRDA.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1779761/+attachment/5158963/+files/PciMultimedia.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-24-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.6
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.6
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+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 1779761] Re: Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

apport information

** Tags added: apport-collected bionic

** Description changed:

  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:
  
  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)
  
  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.
  
  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service
  
  This issues is persistent when running kernel 4.15.0-24.26, i have tried
  multiple reboots.
  
  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.
+ --- 
+ ProblemType: Bug
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-24-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=120326fe-9fa7-4c70-95aa-7448f0ba5ed6
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ Lsusb:
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=56b7f88c-7204-4038-926f-477f130f257a ro
+ ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-24-generic N/A
+  linux-backports-modules-4.15.0-24-generic  N/A
+  linux-firmware 1.173.1
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic
+ Uname: Linux 4.15.0-24-generic x86_64
+ UnreportableReason: This report is about a package that is not installed.
+ UpgradeStatus: Upgraded to bionic on 2018-04-13 (80 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
+ _MarkForUpload: False
+ dmi.bios.date: 04/01/2014
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-i440fx-2.6
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.6:cvnQEMU:ct1:cvrpc-i440fx-2.6:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-2.6
+ dmi.sys.vendor: QEMU

** Attachment added: "AlsaDevices.txt"
   
https://bugs.launchpad.net/bugs/1779761/+attachment/5158959/+files/AlsaDevices.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/1779761

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed,

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

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

apport-collect 1779777

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

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

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

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

** Tags added: bionic

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

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic

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

2018-07-02 Thread Lucas Zanella

I've tested the new kernel with this parameter for 10 days and the error
didn't happen, which is a record. So I decided to open a VM yesterday
and it handled good for like 12 hours, they I went to sleep and grabbed
the computer again and the error had happened inside and outside the VM.
I don't know if it was caused by the VM itself but for those 10 days I
tested, it worked great.

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

[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu

2018-07-02 Thread Explorer09

Look like my comment gets ignored.
In short: Please revert this and fix it properly. Don't let linux-image-generic 
package depend on amd64-microcode or intel-microcode! Change the relationship 
to "Recommends" instead!

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

Title:
  need to ensure microcode updates are available to all bare-metal
  installs of Ubuntu

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  Fix Released
Status in linux-meta-oem package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta source package in Trusty:
  Fix Released
Status in linux-meta source package in Xenial:
  Fix Released
Status in linux-meta-hwe source package in Xenial:
  Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
  Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
  Fix Committed
Status in linux-meta-oem source package in Xenial:
  Fix Released
Status in linux-meta source package in Zesty:
  Invalid
Status in linux-meta source package in Artful:
  Fix Released
Status in linux-meta source package in Bionic:
  Fix Released

Bug description:
  From time to time, CPU vendors release updates to microcode that can
  be loaded into the CPU from the OS.  For x86, we have these updates
  available in the archive as amd64-microcode and intel-microcode.

  Sometimes, these microcode updates have addressed security issues with
  the CPU.  They almost certainly will again in the future.

  We should ensure that all users of Ubuntu on baremetal x86 receive
  these security updates, and have them applied to the CPU in early boot
  where at all feasible.

  Because these are hardware-dependent packages which we don't want to
  install except on baremetal (so: not in VMs or containers), the
  logical place to pull them into the system is via the kernel, so that
  only the kernel baremetal flavors pull them in.  This is analogous to
  linux-firmware, which is already a dependency of the linux-
  image-{lowlatency,generic} metapackages, and whose contents are
  applied to the hardware by the kernel similar to microcode.

  So, please update the linux-image-{lowlatency,generic} metapackages to
  add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
  and the corresponding hwe metapackages also.

  Please time this change to coincide with the next updates of the
  microcode packages in the archive.

  I believe we will also need to promote the *-microcode packages to
  main from restricted as part of this (again, by analogy with linux-
  firmware).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+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 1779777] [NEW] Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Public bug reported:

bcmwl-kernel-source reinstall

Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

depmod

DKMS: install completed.
Building initial module for 4.15.0-24-generic
ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 4.15.0-24-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
update-initramfs: deferring update (trigger activated)
Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic

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

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

Title:
  Wifi Broadcom Limited BCM43142 dont working 4.15.0-24

Status in linux package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source reinstall

  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Building initial module for 4.15.0-24-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/bcmwl-kernel-source.0.crash'
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more 
information.
  update-initramfs: deferring update (trigger activated)
  Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) …
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+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 1778097] Re: bcmwl-kernel-source not working with linux-image-4.15.0-24-generic

2018-07-02 Thread rasaborio

That was the bcmwl driver I was installing to try to fix the problem, it
didn't work until I used 4.15.0.23 kernel version instead of 4.15.0.24

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

Title:
  bcmwl-kernel-source not working with linux-image-4.15.0-24-generic

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  Updated to linux-image-4.15.0-24-generic in my Ubuntu 16.04 LTS 64
  bits and wireless stopped working, as if not present, but installed.

  Log file /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log showed:

  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.15.0-24-generic 
(x86_64)
  mar 19 jun 20:06:46 CST 2018
  make: se entra en el directorio '/usr/src/linux-headers-4.15.0-24-generic'
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_os_get_image_block’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:26: 
warning: passing argument 2 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘void *’ but argument is of type 
‘loff_t {aka long long int}’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:37: 
warning: passing argument 3 of ‘kernel_read’ makes integer from pointer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
   ^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘size_t {aka long unsigned int}’ 
but argument is of type ‘char *’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:42: 
warning: passing argument 4 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘loff_t * {aka long long int *}’ 
but argument is of type ‘int’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  symbolmap: la: invalid section
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_init_timer’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
init_timer(>timer);
^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2360:10: 
error: ‘struct timer_list’ has no member named ‘data’
t->timer.data = (ulong) t;
^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2361:20: 
error: assignment from incompatible pointer type 
[-Werror=incompatible-pointer-types]
t->timer.function = wl_timer;
  ^
  cc1: some warnings being treated as errors
  scripts/Makefile.build:332: fallo en las instrucciones para el objetivo 
'/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o'
  make[1]: *** 
[/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1
  Makefile:1552: fallo en las instrucciones para el objetivo 
'_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build'
  make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error 2
  make: se sale del directorio '/usr/src/linux-headers-4.15.0-24-generic'


  Installing the bcmwl package process:

  Leyendo lista de paquetes... Hecho
  Creando árbol de dependencias   
  Leyendo la información de estado... Hecho
  Se

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-07-02 Thread Skipper

qemu-system-x86 broken when running kernel 4.4.0-130 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).

Totally black screen immediately - no bios flashes.

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

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

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

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-07-02 Thread whl2

Christopher,

1) On 16.04 I was using nvidia driver from Ubuntu packages, but can't really
remember what version. I'm not sure if the history of package installation is
recorded somewhere.
On the other hand, I can try running 16.04 from USB stick with several
different versions of the driver.

2) Sorry, I still didn't test it, will try tomorrow. The single time I
tried it before, it gave a very poor performance, laptop was almost
unusable.

3) Testing 4.18 seems a way easier, I can do it.

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

Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
Incomplete

Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.

Things tried:

Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.

asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.

4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.

Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.

---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

This change was made by a bot.

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

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

Title:
  package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: installed linux-headers-4.15.0-24-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Don't think this is a linux bug, but since Ubuntu auto-generated this
  report I am going to submit it anyway.

  I installed the Paragon UFS tools a while ago, but they don't support
  version 18.04. I assumed the install failed, but apparently it
  actually succeeded but just the dkms step failed. On update this time,
  the dkms step for the linux-headers package again failed, but then
  afterwards the installer just hung, with dkms frozen and using no CPU.
  After about 15 minutes I killed the dkms process which crashed the
  installer and generated this bug.

  My plan now is to reboot and then run the dkms_autoinstall command
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dacre  2293 F...m pulseaudio
   /dev/snd/controlC0:  gdm1670 F pulseaudio
dacre  2293 F pulseaudio
  Date: Mon Jul  2 15:07:48 2018
  ErrorMessage: installed linux-headers-4.15.0-24-generic package 
post-installation script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=7aef2be7-ebae-46f3-9670-155804393c99
  InstallationDate: Installed on 2018-06-19 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LG Electronics 14Z980-A.AAS7U1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/weatherwax_system-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: installed linux-headers-4.15.0-24-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: K2ZC0250 X64
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 14Z980
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrK2ZC0250X64:bd03/08/2018:svnLGElectronics:pn14Z980-A.AAS7U1:pvr0.1:rvnLGElectronics:rn14Z980:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:
  dmi.product.family: Z Series
  dmi.product.name: 14Z980-A.AAS7U1
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779772/+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 1778097] Re: bcmwl-kernel-source not working with linux-image-4.15.0-24-generic

2018-07-02 Thread Pavel Selivanov

Affected me also. To fix it we should download the newer driver that
works with 4.15.+ kernels:

wget http://mirrors.kernel.org/ubuntu/pool/restricted/b/bcmwl/bcmwl-
kernel-source_6.30.223.271+bdcom-0ubuntu4_amd64.deb

sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu4_amd64.deb

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

Title:
  bcmwl-kernel-source not working with linux-image-4.15.0-24-generic

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  Updated to linux-image-4.15.0-24-generic in my Ubuntu 16.04 LTS 64
  bits and wireless stopped working, as if not present, but installed.

  Log file /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log showed:

  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.15.0-24-generic 
(x86_64)
  mar 19 jun 20:06:46 CST 2018
  make: se entra en el directorio '/usr/src/linux-headers-4.15.0-24-generic'
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_os_get_image_block’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:26: 
warning: passing argument 2 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘void *’ but argument is of type 
‘loff_t {aka long long int}’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:37: 
warning: passing argument 3 of ‘kernel_read’ makes integer from pointer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
   ^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘size_t {aka long unsigned int}’ 
but argument is of type ‘char *’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:42: 
warning: passing argument 4 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘loff_t * {aka long long int *}’ 
but argument is of type ‘int’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  symbolmap: la: invalid section
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_init_timer’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
init_timer(>timer);
^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2360:10: 
error: ‘struct timer_list’ has no member named ‘data’
t->timer.data = (ulong) t;
^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2361:20: 
error: assignment from incompatible pointer type 
[-Werror=incompatible-pointer-types]
t->timer.function = wl_timer;
  ^
  cc1: some warnings being treated as errors
  scripts/Makefile.build:332: fallo en las instrucciones para el objetivo 
'/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o'
  make[1]: *** 
[/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1
  Makefile:1552: fallo en las instrucciones para el objetivo 
'_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build'
  make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error 2
  make: se sale del directorio '/usr/src/linux-headers-4.15.0-24-generic'


  Installing the bcmwl

[Kernel-packages] [Bug 1779772] [NEW] package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: installed linux-headers-4.15.0-24-generic package post-installation script subproc

2018-07-02 Thread Mike Dacre

Public bug reported:

Don't think this is a linux bug, but since Ubuntu auto-generated this
report I am going to submit it anyway.

I installed the Paragon UFS tools a while ago, but they don't support
version 18.04. I assumed the install failed, but apparently it actually
succeeded but just the dkms step failed. On update this time, the dkms
step for the linux-headers package again failed, but then afterwards the
installer just hung, with dkms frozen and using no CPU. After about 15
minutes I killed the dkms process which crashed the installer and
generated this bug.

My plan now is to reboot and then run the dkms_autoinstall command
manually.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-24-generic 4.15.0-24.26
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   dacre  2293 F...m pulseaudio
 /dev/snd/controlC0:  gdm1670 F pulseaudio
  dacre  2293 F pulseaudio
Date: Mon Jul  2 15:07:48 2018
ErrorMessage: installed linux-headers-4.15.0-24-generic package 
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=7aef2be7-ebae-46f3-9670-155804393c99
InstallationDate: Installed on 2018-06-19 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LG Electronics 14Z980-A.AAS7U1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/weatherwax_system-root ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: installed linux-headers-4.15.0-24-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2018
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: K2ZC0250 X64
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 14Z980
dmi.board.vendor: LG Electronics
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LG Electronics
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrK2ZC0250X64:bd03/08/2018:svnLGElectronics:pn14Z980-A.AAS7U1:pvr0.1:rvnLGElectronics:rn14Z980:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:
dmi.product.family: Z Series
dmi.product.name: 14Z980-A.AAS7U1
dmi.product.version: 0.1
dmi.sys.vendor: LG Electronics

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: installed linux-headers-4.15.0-24-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Don't think this is a linux bug, but since Ubuntu auto-generated this
  report I am going to submit it anyway.

  I installed the Paragon UFS tools a while ago, but they don't support
  version 18.04. I assumed the install failed, but apparently it
  actually succeeded but just the dkms step failed. On update this time,
  the dkms step for the linux-headers package again failed, but then
  afterwards the installer just hung, with dkms frozen and using no CPU.
  After about 15 minutes I killed the dkms process which crashed the
  installer and generated this bug.

  My plan now is to reboot and then run the dkms_autoinstall command
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dacre  2293 F...m pulseaudio
   /dev/snd/controlC0:  gdm1670 F pulseaudio
dacre  2293 F pulseaudio
  Date: Mon Jul  2 15:07:48 2018
  ErrorMessage: installed linux-headers-4.15.0-24-generic package 
post-installation script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=7aef2be7-ebae-46f3-9670-155804393c99
  InstallationDate: Installed on 2018-06-19 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-07-02 Thread Christopher M. Penalver

whl2:

1) To clarify, when you were using 16.04, were you using the nvidia or
nouveau driver? If nvidia, which version precisely?

2) If you uninstall the nvidia driver in your current OS, and use
nouveau is there any change?

3) To keep this relevant to upstream, one will want to test the latest
mainline kernel (now 4.18-rc3) as it is released. Could you please
advise?

** Changed in: linux (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/1775717

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+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 1779688] Re: RTL8723BE unable to establish connection (fixed in 4.17.x)

2018-07-02 Thread Evgen

** Summary changed:

-  RTL8723BE unable to establish connection
+ RTL8723BE unable to establish connection (fixed in 4.17.x)

** Description changed:

  With kernel version 4.10+ I'm unable to establish WiFi connection.
  Router shows logs:
  Association Success:STA **:*:**:**:**:**
  4-way handshake success:STA **:*:**:**:**:**
  Received Deauth:STA **:*:**:**:**:**(reason 3)
  
  It works well with "rtlwifi_new" drivers or newer mainline kernels
  (4.17.3 & 4.18-rc3 worked; 4.16 & 4.17-rc7 didn't) so probably something
  could be backported from there. Any power-management or ant_sel driver
  options didn't help me. Closest things I managed to find were
  https://patchwork.kernel.org/patch/10196339/ (rtl8821ae keep alive not
  set, connection lostlogin) and commit from rtlwifi repo "rtl8723be: Add
- L1 latency to rtl8723be".
+ L1 latency to rtl8723be"
+ 
(https://github.com/lwfinger/rtlwifi_new/commit/196972510a4d4280b6773398f7f43609c66f8c35)
+ but first is already in 4.15 & second didn't help me so that must be
+ something else...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul  2 16:58:39 2018
  InstallationDate: Installed on 2018-05-31 (32 days ago)
  InstallationMedia: Xubuntu Core 18.04 - amd64 - 20180509
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  With kernel version 4.10+ I'm unable to establish WiFi connection.
  Router shows logs:
  Association Success:STA **:*:**:**:**:**
  4-way handshake success:STA **:*:**:**:**:**
  Received Deauth:STA **:*:**:**:**:**(reason 3)
  
  It works well with "rtlwifi_new" drivers or newer mainline kernels
- (4.17.3 & 4.18-rc3 worked; 4.16 & 4.17-rc7 didn't) so probably something
- could be backported from there. Any power-management or ant_sel driver
- options didn't help me. Closest things I managed to find were
- https://patchwork.kernel.org/patch/10196339/ (rtl8821ae keep alive not
- set, connection lostlogin) and commit from rtlwifi repo "rtl8723be: Add
- L1 latency to rtl8723be"
+ (4.17.3 & 4.18-rc3 worked; 4.16.x & 4.17-rc7 didn't) so probably
+ something could be backported from there. Any power-management or
+ ant_sel driver options didn't help me. Closest things I managed to find
+ were https://patchwork.kernel.org/patch/10196339/ (rtl8821ae keep alive
+ not set, connection lostlogin) and commit from rtlwifi repo "rtl8723be:
+ Add L1 latency to rtl8723be"
  
(https://github.com/lwfinger/rtlwifi_new/commit/196972510a4d4280b6773398f7f43609c66f8c35)
  but first is already in 4.15 & second didn't help me so that must be
  something else...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul  2 16:58:39 2018
  InstallationDate: Installed on 2018-05-31 (32 days ago)
  InstallationMedia: Xubuntu Core 18.04 - amd64 - 20180509
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  With kernel version 4.10+ I'm unable to establish WiFi connection.
  Router shows logs:
  Association Success:STA **:*:**:**:**:**
  4-way handshake success:STA **:*:**:**:**:**
  Received Deauth:STA **:*:**:**:**:**(reason 3)
  
  It works well with "rtlwifi_new" drivers or newer mainline kernels
  (4.17.3 & 4.18-rc3 worked; 4.16.x & 4.17-rc7 didn't) so probably
  something could be backported from there. Any power-management or
  ant_sel driver options didn't help me. Closest things I managed to find
  were https://patchwork.kernel.org/patch/10196339/ (rtl8821ae keep alive
- not set, connection lostlogin) and commit from rtlwifi repo "rtl8723be:
- Add L1 latency to rtl8723be"
- 
(https://github.com/lwfinger/rtlwifi_new/commit/196972510a4d4280b6773398f7f43609c66f8c35)
- but first is already in 4.15 & second didn't help me so that must be
+ not set, connection lostlogin) and commit from "rtlwifi_new" repo
+ ("rtl8723be: Add L1 latency to rtl8723be" -
+ 
https://github.com/lwfinger/rtlwifi_new/commit/196972510a4d4280b6773398f7f43609c66f8c35
+ ) but first is already in 4.15 & second didn't help me so that must be
  something else...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul  2 16:58:39 2018
  InstallationDate: Installed on 2018-05-31 (32 days ago)
  InstallationMedia: Xubuntu Core 18.04 -

[Kernel-packages] [Bug 1779758] Re: zfs utils and kernel version mismath

2018-07-02 Thread Colin Ian King

The zfs kernel module and user space tools have had a compatibility shim
added in the userspace ioctl interface to the kernel to ensure
interoperability with the older userspace tools and the kernel driver.
We have extensively tested the userspace side to confirm that this
works, however, if you do find interoperability issues please file a
separate bug for any issues you find.

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Low

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

Title:
  zfs  utils and kernel version mismath

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  I have 16.04 installed with HWE and did a dist-upgrade. This installed
  a new kernel 4.15 with zfs version 7.5 but did not upgrade the
  zfsutils-linux package.

  I now have a mismatch zfsutils and zfs module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1779758/+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 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

2018-07-02 Thread Luke Williams

So I built a kernel from the Upstream LTS (4.17.3) and tried to apply
the patch, which failed. So I removed it and tried a clean build and was
able to get Xenial to boot up with this kernel. I then decided to
install Bionic and install this kernel on my laptop however, I noticed
that when I downloaded the latest version (as of July 2, 2018) the
laptop display worked. I checked and I am running Bionic with the
4.15.0-24 kernel. I then installed the NVIDIA proprietary drivers and
low and behold the laptop is working. (I had to modify my grub to
include nouveau.modeset=0 since after logging in the display would hang,
but after passing the kernel parameter everything worked out of the
box.)

This is quite amazing! I'm going to check out the ChangeLog to see what
patches you have running on this.

For the most part, things are working normally. I did notice if I try to
go to the TTY1 or TTY2, I get the GNOME login Screen on TTY1 and my
normal desktop on TTY2, but TTY3-6 are standard terminals. The
brightness control keys still do not work, but the touchpad works so far
from initial testing (Haven't tried the 5 finger test on it yet, but 4
fingers works) and the hibernate issue when the lid closes seems to be
fixed since I was able to resume when I opened the laptop and pressed
space bar to turn it back on.

I will continue to test, but we may have a winner winner chicken dinner
for this bug.

Thanks!!

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

Title:
nouveau/nvidia drivers do not work with display in Bionic on Asus
GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
Confirmed

Bug description:
Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
using 3D) and the installer does not display. I have tried
nouveau.modeset=0 and nomodeset boot options to no avail. I was able
to finally install Bionic by hooking up the laptop to a projector, but
after a reboot, the laptop display still did not work and I had to set
the account to autologin otherwise I could not login to the laptop. I
then install openssh-server so that I could ssh into the laptop and I
installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
installed, but still no local display.

In Artful, I could install with the nouveau.modeset=0 and then
installing the proprietary NVIDIA drivers and everything (except
touchpad, LP: 1738263) worked.

lspci shows the graphics card and NVIDIA card, and lsmod does show
that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
i915 for graphcis, and once NVIDIA drivers are install, lsmod only
shows i915 and asus_wmi for graphics while nvidia is used for gpu and
3D, but still no display on the laptop.

lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
lspci.txt shows the detected hardware
lshw.txt shows the hardware in the laptop.

Please let me know if you need any other information.

Thanks,
Luke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+subscriptions

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

2018-07-02 Thread Joseph Salisbury

I built the next test kernel, up to the following commit:
c94dc34f771a25b8c3e0955147fdc4f5e3d79908

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1773113] Re: nvidia-390 does not show GUI

2018-07-02 Thread hoan

Here is a live iso xubuntu-bionic with nvidia-390.48 and prime from
MatheuGras-TimRichardson

It switched correctly on live testing with Acer VN7 laptop 4GB

https://sourceforge.net/projects/toysbox/files/bionic-
nvidia/xubuntu-18.04-4.15.0-24-nvidia.iso

  Screenshots + Logs are on the site

 xubuntu@xubuntu:~$ cat /proc/cmdline BOOT_IMAGE=(loop)/casper/vmlinuz
iso-scan/filename=/iso/xubuntu-18.04-4.15.0-24-nvidia0.iso
file=/cdrom/preseed/xubuntu.seed waitusb=5 boot=casper

xubuntu@xubuntu:~$ uname -a 
Linux xubuntu 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux 

xubuntu@xubuntu:~$ inxi -G 
Graphics: 
Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller 
Card-2: NVIDIA GM107M [GeForce GTX 860M] 
Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: 
fbdev,vesa,nouveau) Resolution: 1920x1080@60.02hz 
OpenGL: renderer: GeForce GTX 860M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.48 

xubuntu@xubuntu:~$ xrandr --listproviders 
Providers: number : 2 
Provider 0: id: 0x23a cap: 0x1, Source Output crtcs: 0 outputs: 0 associated 
providers: 1 name:NVIDIA-0 
Provider 1: id: 0x44 cap: 0x6, Sink Output, Source Offload crtcs: 3 outputs: 2 
associated providers: 1 name:modesetting 

xubuntu@xubuntu:~$ glxinfo | grep NVIDIA 
server glx vendor string: NVIDIA Corporation 
client glx vendor string: NVIDIA Corporation 
OpenGL vendor string: NVIDIA Corporation OpenGL core profile version string: 
4.6.0 NVIDIA 390.48 OpenGL core profile shading language version string: 4.60 
NVIDIA 
OpenGL version string: 4.6.0 NVIDIA 390.48 
OpenGL shading language version string: 4.60 NVIDIA 
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.48 

xubuntu@xubuntu:~$ glxgears 
Running synchronized to the vertical refresh. The framerate should be 
approximately the same as the monitor refresh rate.
 69297 frames in 5.0 seconds = 13859.334 FPS
 68090 frames in 5.0 seconds = 13617.823 FPS 

xubuntu@xubuntu:~$ glxspheres64 Polygons in scene: 62464 (61 spheres * 1024 
polys/spheres) Visual ID of window: 0xa8 Context is Direct OpenGL Renderer: 
GeForce GTX 860M/PCIe/SSE2 
1914.953887 frames/sec - 2137.088538 Mpixels/sec 
1964.035952 frames/sec - 2191.864122 Mpixels/sec

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

Title:
   nvidia-390 does not show GUI

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

Bug description:
  I know this bug is a duplicate, I am opening it because it seems that for # 
#1752053 it is marked as "Fix Released" although many people are still affected 
and complaining about it and nobody can or will change that status. So it is an 
attempt to raise more attention, as HDMI currently isn't usable for me on 
Ubuntu 18.04 (it affected me on 16.04 as well).
  Put in short, after Nvidia drivers are installed and I switch from Nvidia 
card to the intel one, the GUI can't be opened anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773113/+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 1779761] Re: Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Unfortunately this is a production server and i can't keep rebooting the
thing and upgrading and downgrading kernels indefinitely.

If it's absolutely critical to fixing this issue i am, however, willing
tot setup a identical VPS  and run apport-collect.

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

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-07-02 Thread whl2

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

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

apport-collect 1779761

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+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 1764645] Re: Bluetooth not working

2018-07-02 Thread Tim Passingham

The recent 4.15.0-24 kernel also doesn't have patch.

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

Title:
  Bluetooth not working

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

Bug description:
  == SRU Justification ==
  A regression was discovered in Bionic.  The regression was introduced by
  mainline commit f44cb4b19ed4, which then made it's way into Bionic in
  4.15.0-14 as commit c91729972ac6 via stable updates.

  This regression is fixed by mainline commit 803cdb8ce584.  Commit
  803cdb8ce584 was also cc'd to stable.  However, it has not landed in
  upstream stable 4.15 or Bionic.

  
  == Fix ==
  803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012 
models")

  
  == Regression Potential ==
  Low.  This fix has also been cc'd to upstream stable, so it has had
  additonal upstream review.

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



  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth (perfectly working with Xenial). In bluetooth control
  panel the slider is impossible to move to "on".

  1) Ubuntu Release (via 'lsb_release -rd')
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) Version of package (apt-cache policy gnome-bluetooth)
  gnome-bluetooth:
    Installato: 3.28.0-2
    Candidato:  3.28.0-2
    Tabella versione:
   *** 3.28.0-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I expected to switch on the bluetooth.

  4) What happened instead
  Bluetooth won't switch on.

  5) Output of rfkill list is:
  0: hci0: Bluetooth
     Soft blocked: no
     Hard blocked: no
  1: phy0: Wireless LAN
     Soft blocked: no
     Hard blocked: no

  6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
  03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
  Network Adapter [168c:0034] (rev 01)
  Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
  size Mini PCIe Card [1a56:2003]
  Kernel driver in use: ath9k
  Kernel modules: ath9k
  04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
  Ethernet [1969:10a1] (rev 10)
  Bus 002 Device 002: ID 8087:8000 Intel Corp.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
  Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
  AR3012 Bluetooth 4.0
  Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [   17.715399] Bluetooth: Core ver 2.22
  [   17.715414] Bluetooth: HCI device and connection manager initialized
  [   17.715416] Bluetooth: HCI socket layer initialized
  [   17.715418] Bluetooth: L2CAP socket layer initialized
  [   17.715422] Bluetooth: SCO socket layer initialized
  [   17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
  [   18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   18.600649] Bluetooth: BNEP filters: protocol multicast
  [   18.600651] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173

[Kernel-packages] [Bug 1779761] Re: Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Added output of sudo cat /proc/version_signature > version.log


** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+attachment/5158898/+files/version.log

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  New

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+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 1779761] Re: Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Added output of sudo lspci -vnvn > lspci-vnvn.log


** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+attachment/5158899/+files/lspci-vnvn.log

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  New

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+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 1779761] [NEW] Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Public bug reported:

After updating the kernel on my QEMU based VPS running 18.04 Server to
kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
starting:

● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s ago
 Docs: man:php-fpm7.2(8)
  Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
 Main PID: 595 (code=killed, signal=TERM)

jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process Manager...
jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed out. 
Terminating.
jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

This issues is persistent when running kernel 4.15.0-24.26, i have tried
multiple reboots.

After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.

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

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1779761/+attachment/5158897/+files/version.log

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

Title:
  Ubuntu Kernel 4.15.0-24.26 causes php7.2-fpm.service to hang at boot

Status in linux package in Ubuntu:
  New

Bug description:
  After updating the kernel on my QEMU based VPS running 18.04 Server to
  kernel ver. 4.15.0-24.26 i noticed that php7.2-fpm.service was't
  starting:

  ● php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
 Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Mon 2018-07-02 13:38:07 CEST; 15s 
ago
   Docs: man:php-fpm7.2(8)
Process: 595 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config 
/etc/php/7.2/fpm/php-fpm.conf (code=killed, signal=TERM)
   Main PID: 595 (code=killed, signal=TERM)

  jul 02 13:36:39 www systemd[1]: Starting The PHP 7.2 FastCGI Process 
Manager...
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Start operation timed 
out. Terminating.
  jul 02 13:38:07 www systemd[1]: php7.2-fpm.service: Failed with result 
'timeout'.
  jul 02 13:38:07 www systemd[1]: Failed to start The PHP 7.2 FastCGI Process 
Manager.

  Setting timeout of php7.2-fpm.service to 300s i and running systemd-analyze 
blame, after rebooting, i noticed that php7.2-fpm.service takes about 3 minutes 
to start:
  sudo systemd-analyze blame
  2min 54.715s php7.2-fpm.service

  This issues is persistent when running kernel 4.15.0-24.26, i have
  tried multiple reboots.

  After downgrading to Kernel ver. 4.15.0-23.25 the issues is gone.
  Again I've tried multiple reboots of the server running 4.15.0-23.25 and 
PHP7.2-fpm.service starts withing seconds after rebooting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779761/+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 1779758] [NEW] zfs utils and kernel version mismath

2018-07-02 Thread mike Bernson

Public bug reported:

I have 16.04 installed with HWE and did a dist-upgrade. This installed a
new kernel 4.15 with zfs version 7.5 but did not upgrade the zfsutils-
linux package.

I now have a mismatch zfsutils and zfs module.

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

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

** No longer affects: pkg-website

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

Title:
  zfs  utils and kernel version mismath

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have 16.04 installed with HWE and did a dist-upgrade. This installed
  a new kernel 4.15 with zfs version 7.5 but did not upgrade the
  zfsutils-linux package.

  I now have a mismatch zfsutils and zfs module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1779758/+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 1779754] Re: software updater gave error message "there was a problem" bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build

2018-07-02 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1757008, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1757008
   bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit 
declaration of function ‘init_timer’]

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

Title:
  software updater gave error message "there was a problem" bcmwl-
  kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Don't really have much detail - just left it running while I was doing
  other things, if it helps, knocked out wireless net

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-24-generic
  Date: Mon Jul  2 20:56:45 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-10-15 (260 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1779754/+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 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)

2018-07-02 Thread Luiz Angelo Daros de Luca

Shelby,

It is something related to timing or something that is not correctly 
initialized.
I have not seen the problem for sometime now. I'm using 18.04. Did you test it?

I don't know if it is fixed or not in recent releases. Maybe it's just
that something changed that misaligned the planets needed to this bug to
happen.

Did you try to unplug/swap USB devices?

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

Title:
  ubuntu fails to boot with btrfs root (unable to mount root)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  Failing to mount / as btrfs has been haunting btrfs users on ubuntu
  for some time. Coming and going with kernel updates.

  After I upgraded to 17.04, it seems that the problem is back.

  It seems that a non-clean umount reboot always leads to a non-bootable 
system. If I boot into rescue (selecting in grub, not a livecd), kernel can 
find the root partition. I can also boot normally if root=... kernel parameter 
is set with the device name (/dev/sda6) instead of UUID=.
  So, there might be a bug in kernel that does not allow linux to identify the 
boot partition using UUID in some circumstances (probably after a dirt reboot).

  Maybe other distros do some magic at initrd that cleans the btrfs
  problem because some, like opensuse, do uses btrfs as default root fs.
  Anyway, even ubuntu own rescue can boot normally.

  This is a tricky bug to debug as I get no logs written and no
  emergency shell. Just an ugly kernel error and a backstack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686837/+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 1779754] [NEW] software updater gave error message "there was a problem" bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build

2018-07-02 Thread Graham Ashcroft

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

Public bug reported:

Don't really have much detail - just left it running while I was doing
other things, if it helps, knocked out wireless net

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
DKMSKernelVersion: 4.15.0-24-generic
Date: Mon Jul  2 20:56:45 2018
DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
InstallationDate: Installed on 2017-10-15 (260 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  software updater gave error message "there was a problem" bcmwl-
  kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Don't really have much detail - just left it running while I was doing
  other things, if it helps, knocked out wireless net

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-24-generic
  Date: Mon Jul  2 20:56:45 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-10-15 (260 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1779754/+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 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries

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

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

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

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

Title:
  Logitech M535 mouse only pairs successfully after 4-5 tries

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I've had my mouse (Logitech M535) paired and working since upgrading
  to 18.04. I had to re-do the pairing after connecting to a different
  machine and now it takes 4-5 tries of pair/remove to connect the
  mouse, on every reboot / sleep cycle.

  The logs show:
  cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info

  But neither actually seem critical as this is shown upon successful
  pairing as well.

  a bluetoothctl session of a failed pairing:
  [bluetooth]# pair 34:88:5D:3E:A1:A4 
  Attempting to pair with 34:88:5D:3E:A1:A4
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
  Pairing successful
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: no

  The mouse continues in pairing mode.

  When using the gnome-control-center Bluetooth module:
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)

  Finally when it connects:
  [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
  [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 15 07:46:38 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 12-9Q33
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago)
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 5C:51:4F:1D:50:3C  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN 
RX bytes:16702 acl:290 sco:0 events:716 errors:0
TX bytes:44162 acl:142 sco:0 commands:427 errors:0

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

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

[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)

2018-07-02 Thread Shelby Cain

@luizluca

Were you ever able to discover a consistent work-around?  I have
*exactly* the same issue with 16.04 since something like the .67 kernel
and I've exhausted everything I can think of to try and figure out why
it is behaving this way.  The only thing that works (as you yourself
stumbled upon) is hitting 'e' in grub and waiting a bit before allowing
it to continue.

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

Title:
  ubuntu fails to boot with btrfs root (unable to mount root)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  Failing to mount / as btrfs has been haunting btrfs users on ubuntu
  for some time. Coming and going with kernel updates.

  After I upgraded to 17.04, it seems that the problem is back.

  It seems that a non-clean umount reboot always leads to a non-bootable 
system. If I boot into rescue (selecting in grub, not a livecd), kernel can 
find the root partition. I can also boot normally if root=... kernel parameter 
is set with the device name (/dev/sda6) instead of UUID=.
  So, there might be a bug in kernel that does not allow linux to identify the 
boot partition using UUID in some circumstances (probably after a dirt reboot).

  Maybe other distros do some magic at initrd that cleans the btrfs
  problem because some, like opensuse, do uses btrfs as default root fs.
  Anyway, even ubuntu own rescue can boot normally.

  This is a tricky bug to debug as I get no logs written and no
  emergency shell. Just an ugly kernel error and a backstack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686837/+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 1773295] Re: False positive ACPI _PRS error messages

2018-07-02 Thread Alex Hung

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

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

Title:
  False positive ACPI _PRS error messages

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  New platforms have hardware registers for routing table implemented as
  "write once". Once set by UEFI firmware during POST, OS will not be
  able to modify the routing table, and ACPI _PRS method are removed
  according to ACPI spec.

  As a result, generating the error messages "ACPI Exception:
  AE_NOT_FOUND, Evaluating _PRS" in kernel by default does not make
  sense, and they should be muted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1773295/+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 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version

2018-07-02 Thread Joseph Salisbury

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: 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/1768431

Title:
  Request to revert SAUCE patches in the 18.04 SRU and update with
  upstream version

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

Bug description:
  == SRU Justification ==
  This SRU was requested by IBM.  It contains one SAUCE patch and three
  commits from linux.next.

  IBM requested that we revert a set of SAUCE patches from 18.04 and
  replace them with patches from linux-next.  Based on review comments,
  there has been minor changes from the original SAUCE patches and the
  versions in linux-next.

  The first SAUCE patch contains all the changes between the current version
  of SAUCE patches for latest cxlflash patches in bionic and the latest
  version accepted by the community. This only has the needed changes and
  makes it so we don't have to revert and re-apply a high number of patches.
  In addition to the SAUCE patch, IBM requested the 3 additional new patches
  from the linux-next tree.

  == Fixes ==
  UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3
  a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops")
  9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)"
  d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts")

  == Regression Potential ==
  Medium.  All the patches are specific to the cxlflash driver, but there
  are four of them and one is a SAUCE patch.

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


  == Comment: #0 - UMA KRISHNAN  - 2018-04-30 14:41:30 ==
  ---Problem Description---
  Request to revert SAUCE patches from 18.04 and apply the patches from 
next/master.

  Below set of cxlflash patches were submitted to Canonical after they
  were sent to the community. Based on review comments, there has been
  minor changes from that version. This BZ is to request reverting those
  SAUCE patches with the ones that are queued in next/master tree for
  4.18.

  - SAUCE: cxlflash: Preserve number of interrupts for master contexts
  - SAUCE: cxlflash: Avoid clobbering context control register value
  - SAUCE: cxlflash: Add argument identifier names
  - SAUCE: cxlflash: Introduce OCXL backend
  - SAUCE: cxlflash: Hardware AFU for OCXL
  - SAUCE: cxlflash: Read host function configuration
  - SAUCE: cxlflash: Setup function acTag range
  - SAUCE: cxlflash: Read host AFU configuration
  - SAUCE: cxlflash: Setup AFU acTag range
  - SAUCE: cxlflash: Setup AFU PASID
  - SAUCE: cxlflash: Adapter context support for OCXL
  - SAUCE: cxlflash: Use IDR to manage adapter contexts
  - SAUCE: cxlflash: Support adapter file descriptors for OCXL
  - SAUCE: cxlflash: Support adapter context discovery
  - SAUCE: cxlflash: Support image reload policy modification
  - SAUCE: cxlflash: MMIO map the AFU
  - SAUCE: cxlflash: Support starting an adapter context
  - SAUCE: cxlflash: Support process specific mappings
  - SAUCE: cxlflash: Support AFU state toggling
  - SAUCE: cxlflash: Support reading adapter VPD data
  - SAUCE: cxlflash: Setup function OCXL link
  - SAUCE: cxlflash: Setup OCXL transaction layer
  - SAUCE: cxlflash: Support process element lifecycle
  - SAUCE: cxlflash: Support AFU interrupt management
  - SAUCE: cxlflash: Support AFU interrupt mapping and registration
  - SAUCE: cxlflash: Support starting user contexts
  - SAUCE: cxlflash: Support adapter context polling
  - SAUCE: cxlflash: Support adapter context reading
  - SAUCE: cxlflash: Support adapter context mmap and release
  - SAUCE: cxlflash: Support file descriptor mapping
  - SAUCE: cxlflash: Introduce object handle fop
  - SAUCE: cxlflash: Setup LISNs for user contexts
  - SAUCE: cxlflash: Setup LISNs for master contexts
  - SAUCE: cxlflash: Update synchronous interrupt status bits
  - SAUCE: cxlflash: Introduce OCXL context state machine
  - SAUCE: cxlflash: Register for translation errors
  - SAUCE: cxlflash: Support AFU reset
  - SAUCE: cxlflash: Enable OCXL operations

  Also, there are 3 additional patches added to end of this series that we 
would like to request being pulled into the SRU stream. These 3 patches address 
bug fixes.
  The commit ids for the patches queued in next/master tree are,

  768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of 
interrupts for master contexts
  6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering 
context control register value
  fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add

[Kernel-packages] [Bug 1770095] Re: Need fix to aacraid driver to prevent panic

2018-07-02 Thread Joseph Salisbury

** Also affects: linux (Ubuntu Cosmic)
   Importance: Critical
 Assignee: Joseph Salisbury (jsalisbury)
   Status: 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/1770095

Title:
  Need fix to aacraid driver to prevent panic

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

Bug description:
  
  == SRU Justification ==
  A commit introduced in mainline v4.14-rc1 to aacraid
  (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a
  panic may happen under certain recovery situations.

  This regression is fixed by linux-next commit  7d3af7d96af7.

  
  == Fix ==
  7d3af7d96af7 ("scsi: aacraid: Correct hba_send to include iu_type")

  == Regression Potential ==
  Low.  This patch fixes a current regression.  It was cc'd to upstream
  stable, so it has had additonal upstream review.

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


  
  == Comment: #0 - Douglas Miller  - 2018-05-08 15:45:13 ==
  +++ This bug was initially created as a clone of Bug #167565 +++

  A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906)
  introduced a bug whereby a panic may happen under certain recovery
  situations. The following commit fixes that:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=7d3af7d96af7b9f51e1ef67b6f4725f545737da2

  We need this commit backported to Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770095/+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 1779187] Re: Ubuntu 16.04.4: crash can not open dumps: "crash: invalid structure member offset: task_struct_pids"

** Tags added: kernel-da-key

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

Title:
  Ubuntu 16.04.4: crash can not open dumps: "crash: invalid structure
  member offset: task_struct_pids"

Status in Ubuntu on IBM z Systems:
  Triaged
Status in crash package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 on IBM z: crash can not open dumps gathered on 4.13.0-39
  crash: invalid structure member offset: task_struct_pids
  FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

   
  ---uname output---
  Linux fvtc2i 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:41:28 UTC 
2018 s390x s390x s390x GNU/Linux
   
  ---Additional Hardware Info---
  none 

   
  Machine Type = lpar type 3906, model 400 LM2  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   crash vmlinux-4.13.0-39-generic dump.201806150854
  or
  crash vmlinux-4.13.0-39-generic
   
  Userspace tool common name: crash 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: crash,crash-dbgsym  7.1.4-1ubuntu4.2 s390x

  Userspace tool obtained from project website:  na 
   
  We came across this issue while trying to extract traces from a vmcore 
gathered on one of our Ubuntu 16.04 nodes running HWE kernel (4.13)

  It seems crash cannot open this dump

  # crash vmlinux-4.13.0-39-generic dump.201806150854

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "s390x-ibm-linux-gnu"...

  WARNING: cannot determine MAX_PHYSMEM_BITS
  please wait... (gathering task table data)
  crash: invalid structure member offset: task_struct_pids
 FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

  [/usr/bin/crash] error trace: 116ed1ed8 => 116ec4b14 => 116f25eec =>
  116f25e48


  this issue is 100% reproducible. An attempt to analyze the live system
  is failing with exact the same error.

  # crash vmlinux-4.13.0-39-generic

  crash 7.1.4
  ...
  WARNING: cannot determine MAX_PHYSMEM_BITS

  crash: invalid structure member offset: task_struct_pids
 FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

  [/usr/bin/crash] error trace: 1260d1ed8 => 1260c4b14 => 126125eec =>
  126125e48

  
  it seems that crash version 7.2.1 shipped with Ubuntu 18.04 can handle dumps 
taken on kernel 4.13, so we have at least a workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1779187/+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 1770029] Re: broadcom-sta-dkms 6.30.223.271-3~16.04.2: broadcom-sta kernel module failed to build [error: implicit declaration of function ‘init_timer’]

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

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

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

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

Title:
  broadcom-sta-dkms 6.30.223.271-3~16.04.2: broadcom-sta kernel module
  failed to build [error: implicit declaration of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  It was updating the system.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: broadcom-sta-dkms 6.30.223.271-3~16.04.2
  ProcVersionSignature: Ubuntu 4.15.0-13.14~16.04.1-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-20-generic
  Date: Tue May  8 23:00:41 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature: 
dkms:broadcom-sta-dkms:6.30.223.271-3~16.04.2:/var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:2352:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-05-31 (342 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  PackageVersion: 6.30.223.271-3~16.04.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: broadcom-sta
  Title: broadcom-sta-dkms 6.30.223.271-3~16.04.2: broadcom-sta kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1770029/+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 1777257] Re: Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

2018-07-02 Thread Merlin

A recent update has fixed it! 18.04 as released comes with kernel
4.15.0-20-generic, which has the bad video effect. Latest update
(2/7/2018) includes 4.15.0-24-generic, which does not (it works
perfectly).

Thanks for your interest!

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

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

Title:
  Dell Inspiron 17r 5737 Ubuntu 18.04 Video Looks Very Strange

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  When booting 18.04 on my Dell 5737 built-in screen the colours are incorrect 
and the display looks to be of low resolution. This is true whether booting 
from a fresh distribution copy on a memory stick or the subsequent patched 
install. A screenshot:
  https://launchpadlibrarian.net/374791190/2018-06-16%2016.46.54.jpg

  The image on an external monitor is fine, and unplugging the external
  monitor doesn't change anything.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  merlin 1635 F pulseaudio
   /dev/snd/controlC1:  merlin 1635 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5737
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=649ad923-d0b7-420a-a0e8-c5753dea246c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0V3MXK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn0V3MXK:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

apport-collect 1779644

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

Title:
  Ubuntu freeze while trying to connect wifi.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hey, when i  try to connect to some wifis i get as an answer from the system 
a screen freeze and a keyboard freeze.
  So i basically can only shutdown the system when this happens.

  I'm using mainline Kernel 4.17.3 !

  Ubuntu 17.10 - 18.04 versions affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779644/+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 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

2018-07-02 Thread Vasilis

I've tried the kernels from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D 
and the last one that I found workding was the 4.14.52,
I presume that the next one is the 4.15.rc1, which shows the problem.
Are there somewhere more builds in between those two that I can search?

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1779644] Re: Ubuntu freeze while trying to connect wifi.

2018-07-02 Thread Brian Murray

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

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

Title:
  Ubuntu freeze while trying to connect wifi.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hey, when i  try to connect to some wifis i get as an answer from the system 
a screen freeze and a keyboard freeze.
  So i basically can only shutdown the system when this happens.

  I'm using mainline Kernel 4.17.3 !

  Ubuntu 17.10 - 18.04 versions affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779644/+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 1779678] Re: deadlocks in copy_net_ns

2018-07-02 Thread Christian Brauner

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

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

Title:
  deadlocks in copy_net_ns

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Various users have reported hangs happening during network namespace
  creation. This mostly manifests in issues while starting lxc containers,
  and, when triggered, can be seen clearly by running `unshare -n` which
  will simply hang forever. This has been happening randomly for quite a
  few kernel versions now. This has been confirmed on 4.13 from Proxmox
  users (which uses an ubuntu based kernel with few patches), and various
  other older and newer kernels as found by reports in the links [1][2][3]
  below. [2] in particular contains the same symptoms across multiple
  distributions and kernel versions. The posted stack traces do include
  copy_net_ns() on top as well.

  There are races in the network code causing copy_net_ns() to hang
  (seemingly permanently). Some of these are caused by specific types of
  interfaces being in use and have been addressed (various refcount leak
  fixes), but that's not all of them. We've received yet another report
  with the current version 4.15.0-22.24 / 4.15.17 with the same symptoms.

  Processes in this state always have copy_net_ns() on top of their
  /proc/$pid/stack looking like:

  ~/ cat /proc/5228/stack 
  [<0>] copy_net_ns+0xab/0x220
  [<0>] create_new_namespaces+0x11b/0x1e0
  [<0>] unshare_nsproxy_namespaces+0x5a/0xb0
  [<0>] SyS_unshare+0x201/0x3a0
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x

  or

  cat /proc/23900/stack 
  [<0>] copy_net_ns+0xab/0x220
  [<0>] create_new_namespaces+0x11b/0x1e0
  [<0>] copy_namespaces+0x6d/0xa0
  [<0>] copy_process.part.35+0x941/0x1ab0
  [<0>] _do_fork+0xdf/0x3f0
  [<0>] SyS_clone+0x19/0x20
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x

  This randomly affects users of network namespaces (lxc, lxd, docker, PVE
  as well as service units using systemd's PrivateNetwork option and
  various others).

  Upstream there have been a lot of changes to the involved locking
  mechanism since 4.16 and we should try to backport these patches.
  This includes most of Kirill Tkhai's network patches and some others.

  I've been going through the following ones generated via various `git
  log` calls on net/, drivers/net/ (initially limiting to the ones with
  `--author='Kirill Tkhai'` as a starting point.)
  There's also a long list of patches we don't need to pick as they're
  implicitly reverted by 1 later change, provided we include all the
  necessary patches. They seem to be nice to review given that they're a
  progressive change first introducing a flag about async-safety, then
  going through all the affected areas with commit messages detailing
  why/if/how they're safe, followed finally when they're all the same by a
  commit to remove the flag again.

  Orderd newest to oldest
  U .. already in the ubuntu kernel, included due to its order when viewing 
related patches
  P .. should be cherry-picked
  Q .. (just 1) included for completion, will conflict in case backports of the 
patches adding NETDEV_{C,S}VLAN_FILTER_PUSH_INFO, which is probably good as a 
reminder for verification?
  - .. if all other patches are applied, they're made obsolete by 2f635ceeb22b 
("net: Drop pernet_operations::async")

  Q 3f5ecd8a90dd net: Fix coccinelle warning
  P eb7f54b90bd8 kcm: Fix use-after-free caused by clonned sockets
  P 554873e51711 net: Do not take net_rwsem in __rtnl_link_unregister()
  P fc1dd36992bb net: Remove net_rwsem from {, un}register_netdevice_notifier()
  P 328fbe747ad4 net: Close race between {un, }register_netdevice_notifier() 
and setup_net()/cleanup_net()
  P 9e2f6c5d78db netfilter: Rework xt_TEE netdevice notifier
  P e9a441b6e729 xfrm: Register xfrm_dev_notifier in appropriate place
  P 152f253152cc net: Remove rtnl_lock() in nf_ct_iterate_destroy()
  P ec9c780925c5 ovs: Remove rtnl_lock() from ovs_exit_net()
  P 350311aab4c0 security: Remove rtnl_lock() in 
selinux_xfrm_notify_policyload()
  P 10256debb918 net: Don't take rtnl_lock() in wireless_nlevent_flush()
  P f0b07bb151b0 net: Introduce net_rwsem to protect net_namespace_list
  d 8518e9bb98b6 net: Add more comments
  P 4420bf21fb6c net: Rename net_sem to pernet_ops_rwsem
  P 2f635ceeb22b net: Drop pernet_operations::async
  P 094374e5e173 net: Reflect all pernet_operations are converted
  - 67441c2472dd net: Convert nfsd_net_ops
  - dbf7bb443726 net: Convert nfs4blocklayout_net_ops
  - 436de500948e net: Convert nfs4_dns_resolver_ops
  - 5e804a6077dc net: Convert sunrpc_net_ops
  - 855aeba34047 net: Convert rpcsec_gss_net_ops
  P 070f2d7e264a net: Drop NETDEV_UNREGISTER_FINAL
  P 3e0c2dbfea28

[Kernel-packages] [Bug 1779644] [NEW] Ubuntu freeze while trying to connect wifi.

You have been subscribed to a public bug:

Hey, when i  try to connect to some wifis i get as an answer from the system a 
screen freeze and a keyboard freeze.
So i basically can only shutdown the system when this happens.

I'm using mainline Kernel 4.17.3 !

Ubuntu 17.10 - 18.04 versions affected.

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


** Tags: bot-comment
-- 
Ubuntu freeze while trying to connect wifi.
https://bugs.launchpad.net/bugs/1779644
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 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

2018-07-02 Thread Sujith Pandel

** Also affects: dellserver
   Importance: Undecided
   Status: New

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

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1690085]

2018-07-02 Thread alexandre9099

Is there any workaround/solution for this bug? With this problem i can't
reliably have the PC running as a server :(

The bug is almost 1 year old

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

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

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

Bug description:
  Hi,

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

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

  native 17.04 kernel
  4.10.15

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

  Here is kern.log entry when happening :

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

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

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

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-02 Thread Michael Reed

** Changed in: dellserver
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1779605/+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 1779063] Re: Occasional kernel panic on shutdown in ext4 code (dquot_drop)

2018-07-02 Thread Maik Merten

The issue started after upgrading from 17.10 to 18.04. However, at the
same time I also upgraded the CPU from an AMD A12-9800 to the AMD Ryzen
7 2700 (with the rest of the system remaining unchanged). I don't have
the older CPU anymore, so I cannot change back for test purposes. Given
the documented occurrences produced exactly the same call trace I don't
expect this to be an intermittent CPU problem (e.g., causes by a CPU
errata).

I can certainly try an upstream kernel. Sadly the issue occurs only on
rare occasions, so it may take quite a while to be reasonably sure
things are okay.

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779063/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

2018-07-02 Thread Carl Reinke

44c891a does NOT have the bug.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1757008] Re: bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]

2018-07-02 Thread Zhidani Ramadhan

do i have to downgrade my kernel?


On Mon, Jul 2, 2018 at 7:51 PM, Vincent Ladeuil <1757...@bugs.launchpad.net>
wrote:

> Happened today after the upgrade, lost wifi :-/
>
> Linux pump 4.15.0-24-generic #26~16.04.1-Ubuntu SMP Fri Jun 15 14:35:08
> UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> rebooting with an older kernel worked around the issue:
>
> Linux pump 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27
> UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1757008
>
> Title:
>   bcmwl-kernel-source: bcmwl kernel module failed to build [error:
>   implicit declaration of function ‘init_timer’]
>
> Status in bcmwl package in Ubuntu:
>   Confirmed
> Status in broadcom-sta package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The module fails to build, as it is missing the necessary patches for
>   the latest HWE kernel.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
>   ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
>   Uname: Linux 4.13.0-36-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: amd64
>   DKMSKernelVersion: 4.15.0-13-generic
>   Date: Mon Mar 19 15:02:46 2018
>   DuplicateSignature: dkms:bcmwl-kernel-source:6.30.
> 223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.
> 271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration
> of function ‘init_timer’ [-Werror=implicit-function-declaration]
>   InstallationDate: Installed on 2017-06-05 (287 days ago)
>   InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
> (20170215.2)
>   PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.4
>apt  1.2.26
>   SourcePackage: bcmwl
>   Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl
> kernel module failed to build
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/
> 1757008/+subscriptions
>

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

Title:
  bcmwl-kernel-source: bcmwl kernel module failed to build [error:
  implicit declaration of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1757008/+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 1757008] Re: bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]

2018-07-02 Thread Zhidani Ramadhan

do i have to downgrade my kernel?

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

Title:
  bcmwl-kernel-source: bcmwl kernel module failed to build [error:
  implicit declaration of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2018-07-02 Thread Brad Figg

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1779354
  phase: Uploaded

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779354
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779361/+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 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

2018-07-02 Thread Andrew Cloke

Looking at the kernel SRU mail archives, this has been NACK'ed for
Artful as Artful will EOL shortly.

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  In Progress
Status in makedumpfile source package in Artful:
  Incomplete

Bug description:
  == SRU Justification ==
  IBM has requested these three commits in Artful.  In Artful, kdump fails to
  capture dump when smt=2 or off.

  Including these three commits allows kdump to work properly.

  == Fixes ==
  4388c9b3a6ee ("powerpc: Do not send system reset request through the oops 
path")
  04b9c96eae72 ("powerpc/crash: Remove the test for cpu_online in the IPI 
callback")
  4552d128c26e ("powerpc: System reset avoid interleaving oops using die 
synchronisation")

  == Regression Potential ==
  Low.  Fixes are limited to powerpc.

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



  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048
  [0.004120] NUMA
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 

  [0.004204] GPR04: 0001 0002  
ffdf
  [0.004204] GPR08:  2804 0002 
0002
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378
  [0.004204] GPR20: 0060 1eca 0a6c 
0007
  [0.004204] GPR24:   c9621ed0 

  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        

  [0.004484]        

  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512]
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048
  [0.004526] NUMA
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0
  [0.004611] GPR00:  c95dfda0 c95e3000 

  [0.004611] GPR04:    

  [0.004611] GPR08:  22002228 7fff 
0008
  [0.004611] GPR12:  cfff0a80

[Kernel-packages] [Bug 1779358] Re: linux-aws: 4.15.0-1012.12 -proposed tracker

2018-07-02 Thread Brad Figg

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1779354
  phase: Uploaded

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779354
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779358/+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 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

** Changed in: ubuntu-power-systems
   Status: New => Triaged

** Tags added: kernel-key

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

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

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   73.058099] GPR28: 0063 0004 c1572b1c 
c15e9e68
  [   73.059060] NIP [c07f24c8] sysrq_handle_crash+0x28/0x30
  [   73.059142] LR [c07f3568]

[Kernel-packages] [Bug 1770095] Re: Need fix to aacraid driver to prevent panic

It's already in the SRU process, got already two acks and will be
released with the end of the netxt SRU cycle.

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

Title:
  Need fix to aacraid driver to prevent panic

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

Bug description:
  
  == SRU Justification ==
  A commit introduced in mainline v4.14-rc1 to aacraid
  (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a
  panic may happen under certain recovery situations.

  This regression is fixed by linux-next commit  7d3af7d96af7.

  
  == Fix ==
  7d3af7d96af7 ("scsi: aacraid: Correct hba_send to include iu_type")

  == Regression Potential ==
  Low.  This patch fixes a current regression.  It was cc'd to upstream
  stable, so it has had additonal upstream review.

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


  
  == Comment: #0 - Douglas Miller  - 2018-05-08 15:45:13 ==
  +++ This bug was initially created as a clone of Bug #167565 +++

  A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906)
  introduced a bug whereby a panic may happen under certain recovery
  situations. The following commit fixes that:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=7d3af7d96af7b9f51e1ef67b6f4725f545737da2

  We need this commit backported to Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770095/+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 1776346] Re: linux-azure: 4.15.0-1014.14~16.04.1 -proposed tracker

2018-07-02 Thread Brad Figg

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Monday, 02. July 2018 14:17 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1776338
- phase: Promoted to updates
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Monday, 02. July 2018 14:17 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-azure: 4.15.0-1014.14~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776346/+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 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version

2018-07-02 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  Request to revert SAUCE patches in the 18.04 SRU and update with
  upstream version

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

Bug description:
  == SRU Justification ==
  This SRU was requested by IBM.  It contains one SAUCE patch and three
  commits from linux.next.

  IBM requested that we revert a set of SAUCE patches from 18.04 and
  replace them with patches from linux-next.  Based on review comments,
  there has been minor changes from the original SAUCE patches and the
  versions in linux-next.

  The first SAUCE patch contains all the changes between the current version
  of SAUCE patches for latest cxlflash patches in bionic and the latest
  version accepted by the community. This only has the needed changes and
  makes it so we don't have to revert and re-apply a high number of patches.
  In addition to the SAUCE patch, IBM requested the 3 additional new patches
  from the linux-next tree.

  == Fixes ==
  UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3
  a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops")
  9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)"
  d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts")

  == Regression Potential ==
  Medium.  All the patches are specific to the cxlflash driver, but there
  are four of them and one is a SAUCE patch.

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


  == Comment: #0 - UMA KRISHNAN  - 2018-04-30 14:41:30 ==
  ---Problem Description---
  Request to revert SAUCE patches from 18.04 and apply the patches from 
next/master.

  Below set of cxlflash patches were submitted to Canonical after they
  were sent to the community. Based on review comments, there has been
  minor changes from that version. This BZ is to request reverting those
  SAUCE patches with the ones that are queued in next/master tree for
  4.18.

  - SAUCE: cxlflash: Preserve number of interrupts for master contexts
  - SAUCE: cxlflash: Avoid clobbering context control register value
  - SAUCE: cxlflash: Add argument identifier names
  - SAUCE: cxlflash: Introduce OCXL backend
  - SAUCE: cxlflash: Hardware AFU for OCXL
  - SAUCE: cxlflash: Read host function configuration
  - SAUCE: cxlflash: Setup function acTag range
  - SAUCE: cxlflash: Read host AFU configuration
  - SAUCE: cxlflash: Setup AFU acTag range
  - SAUCE: cxlflash: Setup AFU PASID
  - SAUCE: cxlflash: Adapter context support for OCXL
  - SAUCE: cxlflash: Use IDR to manage adapter contexts
  - SAUCE: cxlflash: Support adapter file descriptors for OCXL
  - SAUCE: cxlflash: Support adapter context discovery
  - SAUCE: cxlflash: Support image reload policy modification
  - SAUCE: cxlflash: MMIO map the AFU
  - SAUCE: cxlflash: Support starting an adapter context
  - SAUCE: cxlflash: Support process specific mappings
  - SAUCE: cxlflash: Support AFU state toggling
  - SAUCE: cxlflash: Support reading adapter VPD data
  - SAUCE: cxlflash: Setup function OCXL link
  - SAUCE: cxlflash: Setup OCXL transaction layer
  - SAUCE: cxlflash: Support process element lifecycle
  - SAUCE: cxlflash: Support AFU interrupt management
  - SAUCE: cxlflash: Support AFU interrupt mapping and registration
  - SAUCE: cxlflash: Support starting user contexts
  - SAUCE: cxlflash: Support adapter context polling
  - SAUCE: cxlflash: Support adapter context reading
  - SAUCE: cxlflash: Support adapter context mmap and release
  - SAUCE: cxlflash: Support file descriptor mapping
  - SAUCE: cxlflash: Introduce object handle fop
  - SAUCE: cxlflash: Setup LISNs for user contexts
  - SAUCE: cxlflash: Setup LISNs for master contexts
  - SAUCE: cxlflash: Update synchronous interrupt status bits
  - SAUCE: cxlflash: Introduce OCXL context state machine
  - SAUCE: cxlflash: Register for translation errors
  - SAUCE: cxlflash: Support AFU reset
  - SAUCE: cxlflash: Enable OCXL operations

  Also, there are 3 additional patches added to end of this series that we 
would like to request being pulled into the SRU stream. These 3 patches address 
bug fixes.
  The commit ids for the patches queued in next/master tree are,

  768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of 
interrupts for master contexts
  6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering 
context control register value
  fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument 
identifier names
  863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL 
backend

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