date:20180704

So maybe it's caused by userspace... you can try older Ubuntu in http
://old-releases.ubuntu.com

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

Title:
  Blu-ray burner no longer detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Kernel 97 is the last kernel in which my Blu-ray burner is still
  detected. Booting with all following kernels makes it undetectable,
  and I can't use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-103-generic 4.4.0-103.126
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  misthalu   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 12 08:00:12 2017
  HibernationDevice: RESUME=UUID=d22d1aa7-36b9-44ab-936e-f713d1f79a40
  InstallationDate: Installed on 2016-05-19 (571 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp8s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=9b2e1b7a-2bbd-4a36-990f-6ba56f567b2d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-Gaming 3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Daniel,

Installing haveged fixed my issue so I'm pretty sure its the same as
this one. Therefore I won't create a bug of my own.

Thanks for the help.

-- 
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
  --- 
  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 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  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
  modified.conffile..etc.gdm3.custom.conf: [modified]
  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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

The fix for 18.04 is now available for testing, in bionic proposed.

If you would like to just download and test the debs directly they are here:
https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1/+build/15084683

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1780165] Re: tc does not display value of prio and quantum options of htb on bionic

2018-07-04 Thread fumihiko kakuma

** Description changed:

  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.
  
  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #
  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $
  
  I sent the patch for this bug to ML of upstream.
  
  https://www.spinics.net/lists/netdev/msg511127.html
+ 
+ I think that the above patch can be applied for the bionic.

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

  I think that the above patch can be applied for the bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1780165/+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 1780165] Re: tc does not display value of prio and quantum options of htb

2018-07-04 Thread fumihiko kakuma

** Description changed:

  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.
  
  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #
  
+ $ lsb_release -a
+ No LSB modules are available.
+ Distributor ID: Ubuntu
+ Description:Ubuntu 18.04 LTS
+ Release:18.04
+ Codename:   bionic
+ $ uname -a
+ Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
+ $ dpkg -l | grep iproute
+ ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
+ $
+ 
  I sent the patch for this bug to ML of upstream.
  
  https://www.spinics.net/lists/netdev/msg511127.html

** Summary changed:

- tc does not display value of prio and quantum options of htb
+ tc does not display value of prio and quantum options of htb on bionic

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1780165/+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 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

2018-07-04 Thread Frank Heimes

Did you passed the following boot parameter while installing 18.04 from 
proposed?
"apt-setup/proposed=true"

https://bugs.launchpad.net/ubuntu/+source/debian-
installer/+bug/1773973/comments/10

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

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

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

Bug description:
  Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot
  with 4.15.0-22-generic and is in a reboot cycle.

  ```
  Exiting petitboot. Type 'exit' to return.
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1
  [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2
  [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec
  [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1]
  [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV
  [2.660462] Modules linked in:
  [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic 
#24-Ubuntu
  [2.660549] NIP:  c000b9ec LR:  CTR: 

  [2.660603] REGS: c0003fd0bd40 TRAP: 0300   Not tainted  
(4.15.0-22-generic)
  [2.660657] MSR:  90001031   CR:   XER: 

  [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 
SOFTE: -4611686018408771536 
  [2.660713] GPR00:  7fffcd511100  
 
  [2.660713] GPR04:    
 
  [2.660713] GPR08:    
 
  [2.660713] GPR12: 75501b231700 000200f0  
 
  [2.660713] GPR16:    
 
  [2.660713] GPR20:    
 
  [2.660713] GPR24:    
 
  [2.660713] GPR28:    
 
  [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [2.661249] LR []   (null)
  [2.661285] Call Trace:
  [2.661303] Instruction dump:
  [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090 
  [2.661387] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 4810 
  [2.661445] ---[ end trace b607b09fe6490607 ]---
  […]
  ```

  Please find the full log attached. Selecting Linux 4.4.0-124-generic
  works.

  ```
  $ uname -a
  Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP 
Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
  $ dpkg -l linux-image-4.15.0-22-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version
Architecture   Description
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 23 16:40 seq
   crw-rw 1 root audio 116, 33 May 23 16:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1759644] Re: [18.04] Regression: wired network does not work upon resume from suspend

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

** This bug has been marked a duplicate of bug 1752772
   r8169 ethernet card don't work after returning from suspension

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

Title:
  [18.04] Regression: wired network does not work upon resume  from
  suspend

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

Bug description:
  After upgrade to 18.04 (bionic) I've encountered the following
  regression: wired network connection does not work, when system is
  resumed from suspend.

  Reloading the kernel driver module seems to help:
  sudo modprobe -r r8169
  sudo modprobe r8169

  Could this be fixed structurally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 20:08:20 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-06 (811 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  ethernet  
1522260260  wo 28 mrt 2018 20:04:20 CEST  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/3  yes enp5s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
   dzente  a899e56b-4048-43a8-bc38-9212d0af383b  wifi  
1493769143  wo 03 mei 2017 01:52:23 CEST  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- 
--  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp5s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/4  
Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp4s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1673 F pulseaudio
   /dev/snd/controlC0:  alexei 1673 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (812 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux

[Kernel-packages] [Bug 1724863] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 [error: ‘struct net_device’ has no member named ‘last_rx’]

2018-07-04 Thread Diego

I had this problem WITH the package bcmwl-kernel-source 6.30.223.271
+bdcom-0ubuntu1~1.2. But found the solution here:
https://elementaryos.stackexchange.com/questions/15842/bcm43142-and-
linux-kernel-4-15-0-24-generic

"I had to download the package for 18.04LTS
(https://packages.ubuntu.com/bionic/bcmwl-kernel-source) and install it
using:

sudo apt-get remove --purge bcmwl-kernel-source
sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu4_amd64.deb"

That worked perfectly for me. Fortunately, I found this solution before 
rebooting so I've never lost conection in the process.
My ubuntu kernel is 16.04.13. My wifi card is BCM4313 802.11bgn.

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3 [error: ‘struct net_device’ has no member
  named ‘last_rx’]

Status in bcmwl package in Ubuntu:
  In Progress
Status in bcmwl source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package bcmwl-kernel-source fails to install in
  supported custom kernels that are based on 4.11 or 4.13. That includes
  the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and
  some of the custom and cloud kernels as well.

  [Test Case]

  Install the bcmwl-kernel-source package with the 4.13 hwe-edge kernel
  from -proposed. The package installation should proceed without any
  errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel version.

  Besides that the new package was tested with the following kernels in an
  amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1724863/+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 1779413] Re: Bluetooth bug

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

OK, thanks. If it fails after "falling into a dream" then this sounds
like bug 1246981, which may be related to the more recent bug 1779289.

** This bug has been marked a duplicate of bug 1246981
   Bluetooth mouse fails to re-connect after sleep.

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

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  ---

[Kernel-packages] [Bug 1762604] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build

2018-07-04 Thread Diego

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

btw... I'm on Ubuntu 16.04LTS

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  After update of linux kernel to 4.13.0-38.generic, my wireless wifi is
  not working anymore.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-38-generic
  Date: Wed Apr  4 18:13:31 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10:
 error: ‘struct net_device’ has no member named ‘last_rx’
  InstallationDate: Installed on 2017-04-21 (353 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: 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/1762604/+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 1762604] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build

2018-07-04 Thread Diego

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

Same problem here, but fixed from:
https://elementaryos.stackexchange.com/questions/15842/bcm43142-and-
linux-kernel-4-15-0-24-generic

"I had to download the package for 18.04LTS
(https://packages.ubuntu.com/bionic/bcmwl-kernel-source) and install it
using:

sudo apt-get remove --purge bcmwl-kernel-source
sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu4_amd64.deb"

That worked perfectly for me. Fortunately, I found this solution before
rebooting so I've never lost conection in the process.

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  After update of linux kernel to 4.13.0-38.generic, my wireless wifi is
  not working anymore.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-38-generic
  Date: Wed Apr  4 18:13:31 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10:
 error: ‘struct net_device’ has no member named ‘last_rx’
  InstallationDate: Installed on 2017-04-21 (353 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: 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/1762604/+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 1779413] Re: Bluetooth bug

2018-07-04 Thread John Daniels

The mouse is connected only after its removal and reboot of the
bluetooth. But as soon as the mouse turns off falling into a dream, you
have to remove it again and restart the bluetooth. Pair does not happen.

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

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pocoz

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

I find it disturbing we still have parts of the system that will block
start-up waiting for entropy. That's not a good user experience.

But maybe that's not the same problem as njsf is experiencing...

njsf: Do you find an older kernel fixes the problem for you too? Try one
of these:

  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.53/
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14927311

You may also want to try:

  sudo apt install haveged

-- 
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
  --- 
  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 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  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
  modified.conffile..etc.gdm3.custom.conf: [modified]
  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 1780118] Re: linux-gcp: 4.15.0-1012.12 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

Title:
  linux-gcp: 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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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: 1780112
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780118/+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 1730775] Re: [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

2018-07-04 Thread quanxian

hi, Anthony

Please make sure this commit had been into Bionic. Thanks

#git branch --contains f2a659f7d8d5da803836583aa16df06bdf324252
* v4.17-rc6
# git tag --contains f2a659f7d8d5da803836583aa16df06bdf324252
v4.17-rc1
...


commit f2a659f7d8d5da803836583aa16df06bdf324252
Author: Mika Westerberg 
Date: Tue Dec 19 12:44:56 2017 +0300

thunderbolt: Resume control channel after hibernation image is created

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

Title:
  [Feature][CFL][ICL] [CNL]Thunderbolt support (Titan Ridge)

Status in intel:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  This is platform independent and can be verified on any of the three 
platforms mentioned here.
  ICL TBT support requires native mode.

  Target Kernel: 4.17
  Target Release: 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730775/+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 1780115] Re: linux-aws: 4.15.0-1013.13 -proposed tracker

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow 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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

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

2018-07-04 Thread Khaled El Mously

** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.15.0-1014.14 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-kvm: 4.15.0-1014.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow 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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780119/+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 1779413] Re: Bluetooth bug

Also, does the mouse never connect at all? Or just not reconnect on
login or on resume from suspend?

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

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

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pocoz  2614 F...m pulseaudio

[Kernel-packages] [Bug 1780115] Re: linux-aws: 4.15.0-1013.13 -proposed tracker

2018-07-04 Thread Khaled El Mously

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.15.0-1013.13 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow 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:
  New
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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** 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
  
  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.15.0-26.28 -proposed tracker

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

  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780112/+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 1780120] Re: linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

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

Title:
  linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780120/+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 1780165] [NEW] tc does not display value of prio and quantum options of htb

2018-07-04 Thread fumihiko kakuma

Public bug reported:

For example when I execute the following commandline, tc does not
display value of prio and quantum option.

# tc qdisc add dev eno2 root handle 1: htb default 10
# tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
# tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
# tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
# tc -d class show dev eno2
class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit linklayer 
ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
#

I sent the patch for this bug to ML of upstream.

https://www.spinics.net/lists/netdev/msg511127.html

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

** Summary changed:

- tc does not to display prio and quantum options of htb
+ tc does not display value of prio and quantum options of htb

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

Title:
  tc does not display value of prio and quantum options of htb

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

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

2018-07-04 Thread bugproxy

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

--- Comment From kalsh...@in.ibm.com 2018-07-04 19:32 EDT---
Please pass below boot parameter while you install 18.04 from proposed repo.

"apt-setup/proposed=true"

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

Title:
  Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting
  with 4.15.0-22-generic kernel.

Status in The Ubuntu-power-systems project:
  New
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Incomplete

Bug description:
  ---Problem Description---

  Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting
  with 4.15.0-22-generic kernel.

  ---Environment--
  Kernel Build:   4.15.0-22-generic
  System Name :  ltc-garri1
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  Unable to boot.

  ---Steps to reproduce--

  1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com
  /ubuntu-ports/dists/bionic/main/installer-
  ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to
  boot.

  ---Logs

  Attaching console lob.

  [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec
  [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11]
  [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV
  [4.578301] Modules linked in:
  [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G  D  
4.15.0-22-generic #24-Ubuntu
  [4.578371] NIP:  c000b9ec LR:  CTR: 

  [4.578413] REGS: c0003febbd40 TRAP: 0300   Tainted: G  D  
 (4.15.0-22-generic)
  [4.578460] MSR:  90001031   CR:   XER: 

  [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 
SOFTE: -4611686018403131680 
  [4.578504] GPR00:  7b0dd870  
 
  [4.578504] GPR04:    
 
  [4.578504] GPR08:    
 
  [4.578504] GPR12: 75dcd8781700 0002b200  
 
  [4.578504] GPR16:    
 
  [4.578504] GPR20:    
 
  [4.578504] GPR24:    
 
  [4.578504] GPR28:    
 
  [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [4.616210] LR []   (null)
  [4.616237] Call Trace:
  [4.616768] Instruction dump:
  [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090 
  [4.617697] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 63ff 
  [4.618195] ---[ end trace a0d70ba94f583cca ]---
  [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd
  [4.782923] 
  [4.783061] Key type encrypted registered
  [4.783087] AppArmor: AppArmor sha1 policy hashing enabled
  [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
  [4.783181] evm: HMAC attrs: 0x1
  [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 
UTC (1527580169)
  [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [4.807260] Freeing unused kernel memory: 4800K
  [4.807321] This architecture does not have kernel memory protection.

  
  == Comment: #2 - SEETEENA THOUFEEK  - 2018-05-29 
06:47:06 ==
  Symptoms looks exactly like 
  .
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978
  .
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+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-04 Thread Carl Reinke

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

[Kernel-packages] [Bug 1775016] Re: [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and simi

2018-07-04 Thread David Gil

This just in, given that I currently use Linux 4.10.17-041017-generic
(x86_64), here is my situation as of now:

1. I was in Twitter.
2. I was trying to type my tweet
3. The up button temporarily does not work but other buttons do work
4. And when I press other keys and mouse, **the up button works again like it 
refuses to get stuck**

And I just tested the up button here in my typing of this comment and
the cursor does go up.

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

Title:
  [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working
  in the middle of typing when running firefox and when running the
  terminal (sudo su) and similar programs until reboot.

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu/Xubuntu 18.04 LTS bug

  What should have happened: Keyboard should have been working no matter
  the processes

  What happened instead: Keyboard stops working in the middle of typing
  when running firefox and when running the terminal as (sudo su) and
  similar programs. I cannot even type a password. Keyboard only works
  again after a reboot.

  xserver-xorg:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  xserver-xorg-input-all:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jun  4 22:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0493]
  InstallationDate: Installed on 2018-06-04 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal"
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0X8R3Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

** 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: 1780112
  phase: Uploaded

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

Title:
  linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

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

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

** 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: 1780112
  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/1780118

Title:
  linux-gcp: 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-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: 1780112
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780118/+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-04 Thread Brad

I had to purge/reinstall lightdm for some reason (otherwise it was
flickering on/off), but now both GDM and LightDM are working as they
should on 4.15.0-24 with 'haveged' installed.

-- 
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
  --- 
  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 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  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
  modified.conffile..etc.gdm3.custom.conf: [modified]
  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 1780124] Re: linux-gcp: 4.15.0-1012.12~16.04.1 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 22:31 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 04. July 2018 22:31 UTC
- kernel-stable-phase:Uploaded
+ 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/1780124

Title:
  linux-gcp: 4.15.0-1012.12~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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 Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780124/+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-04 Thread Brad

I should add that I've only tested this with 'startx' and GDM; I haven't
tried LightDM.

-- 
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
  --- 
  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 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  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
  modified.conffile..etc.gdm3.custom.conf: [modified]
  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 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

2018-07-04 Thread Brad

I believe I found a solution (or at least, a temporary workaround until
the potential bug is fixed). It seemed the bug was introduced in
4.15.0-24, as 4.15.0-23 works fine. I'm running an up-to-date 18.04
system on top of a Lenovo ThinkPad Yoga.

I would get a blank screen with both GDM and LightDM until I started
switching virtual terminals or typing my login info, at which point, it
would just start up seemingly at random. I set systemd to boot to multi-
user instead of graphical, and ran 'startx' and experienced the exact
same delay. I took a look at the startx script source and I traced it
down to a call to /usr/bin/mcookie which generates a magic number to be
used with xauth. According to the BUGS section in the mcookie manpage,
it states that mcookie assumes that "none of the randomness sources will
block." Sure enough, doing an strace on mcookie shows it hangs at a call
to getrandom(), which I'm assuming (my knowledge is a little fuzzy here)
means that entropy is too low for getrandom() to generate a number.
Moving the mouse around, typing a few characters or switching virtual
terminals, to my knowledge, all generate some entropy so that finally
when there's enough, getrandom() returns a number to mcookie, thus
allowing xorg to start.

TL;DR: I installed 'haveged' from the repo, which, as far as I
understand, adds to the entropy on boot, allowing xorg to start without
any delay.

My next step is to take a look at the changelog between kernel releases
and see what I can come up with as a potential cause, but I figured I
would post what I've found so that others may benefit in the meantime.

-- 
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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04

[Kernel-packages] [Bug 1779950] Re: problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

2018-07-04 Thread Nataraj

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  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:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779950/+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 1678665] Re: mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND

2018-07-04 Thread Ubfan

After the 4.15.0-124 kernel update, I started noticing the mei_me error 
messages at the initial startup screen (which usually only had tpm errors), 
although othing fails to work.  
$ dmesg |fgrep mei
[ 2022.278241] mei_me :00:16.0: hbm: properties response: wrong status = 1 
CLIENT_NOT_FOUND
[ 2022.278246] mei_me :00:16.0: mei_irq_read_handler ret = -71.
[ 2022.278281] mei_me :00:16.0: unexpected reset: dev_state = INIT_CLIENTS 
fw status = 1E000245 6006 
[ 6477.968336] mei_me :00:16.0: hbm: properties response: wrong status = 1 
CLIENT_NOT_FOUND
[ 6477.968342] mei_me :00:16.0: mei_irq_read_handler ret = -71.
[ 6477.968374] mei_me :00:16.0: unexpected reset: dev_state = INIT_CLIENTS 
fw status = 1E000245 6006 
[42278.652813] mei_me :00:16.0: hbm: properties response: wrong status = 1 
CLIENT_NOT_FOUND
[42278.652818] mei_me :00:16.0: mei_irq_read_handler ret = -71.
[42278.652852] mei_me :00:16.0: unexpected reset: dev_state = INIT_CLIENTS 
fw status = 1E000245 6006 
$ uname -a
Linux leno 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic
BIOS Revision: 1.42
Firmware Revision: 1.36
Vendor: LENOVO
Version: 8BET62WW (1.42 )
Release Date: 07/26/2013
System Information
Manufacturer: LENOVO
Product Name: 42763JU
Version: ThinkPad W520

Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: A7 06 02 00 FF FB EB BF
Signature: Type 0, Family 6, Model 42, Stepping 7
Version: Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz
Voltage: 1.2 V
External Clock: 100 MHz
Max Speed: 2400 MHz
Current Speed: 2400 MHz

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

Title:
  mei_me :00:16.0: hbm: properties response: wrong status = 1
  CLIENT_NOT_FOUND

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

Bug description:
  dmesg:
  [ 2089.236192] mei_me :00:16.0: hbm: properties response: wrong status = 
1 CLIENT_NOT_FOUND
  [ 2089.236196] mei_me :00:16.0: mei_irq_read_handler ret = -71.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2083 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2083 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Apr  2 16:59:22 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (616 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1678665/+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 1678665] Re: mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND

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

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

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

Title:
  mei_me :00:16.0: hbm: properties response: wrong status = 1
  CLIENT_NOT_FOUND

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

Bug description:
  dmesg:
  [ 2089.236192] mei_me :00:16.0: hbm: properties response: wrong status = 
1 CLIENT_NOT_FOUND
  [ 2089.236196] mei_me :00:16.0: mei_irq_read_handler ret = -71.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2083 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2083 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Apr  2 16:59:22 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (616 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1678665/+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 1780117] Re: linux-azure: 4.15.0-1016.16 -proposed tracker

** 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: 1780112
  phase: Uploaded

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

Title:
  linux-azure: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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: 1780112
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780117/+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 1759644] Re: [18.04] Regression: wired network does not work upon resume from suspend

2018-07-04 Thread Alexey Balmashnov

Sorry for late reply. Fixed in 4.15.0.24.26. Just checked changelog,
indeed #1752772 fixed in this kernel version.

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

Title:
  [18.04] Regression: wired network does not work upon resume  from
  suspend

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

Bug description:
  After upgrade to 18.04 (bionic) I've encountered the following
  regression: wired network connection does not work, when system is
  resumed from suspend.

  Reloading the kernel driver module seems to help:
  sudo modprobe -r r8169
  sudo modprobe r8169

  Could this be fixed structurally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 20:08:20 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-06 (811 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  ethernet  
1522260260  wo 28 mrt 2018 20:04:20 CEST  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/3  yes enp5s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
   dzente  a899e56b-4048-43a8-bc38-9212d0af383b  wifi  
1493769143  wo 03 mei 2017 01:52:23 CEST  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- 
--  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp5s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/4  
Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp4s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1673 F pulseaudio
   /dev/snd/controlC0:  alexei 1673 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
  InstallationDate: Installed on 2016-01-06 (812 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (7 days ago)
  UserGroups: adm

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-07-04 Thread Colin Law

I believe the bug should not be affecting more people as it is not
present in current kernels.  Also 17.10 goes end of life in a few weeks.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1779950] Re: problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

2018-07-04 Thread Magnus

Perhaps you can set the status of this bug to "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/1779950

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  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:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 21:00 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 --
  kernel-stable-master-bug: 1780112
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 04. July 2018 21:00 UTC
+ 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/1780118

Title:
  linux-gcp: 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-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 --
  kernel-stable-master-bug: 1780112
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780118/+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 1779893] Re: my laptop freezes at the login screen

2018-07-04 Thread Luigi Iapichino

Thanks for your feedback.

Joseph, the issue started after updating the kernel to 4.4.0-128. The
version 4.4.0-127 is the last one working correctly. The issue started
as a sound driver problem (drivers were somehow completely gone), but
when I first experienced it I could still login. Afterwards it started
freezing at the login screen. This corroborates the comment from
Oleksii.

For testing the latest upstream kernel, I followed the procedure
described in the page you provided. Unfortunately, while installing the
kernel files, I had an issue with a dependency from libssl1.1 which is
not installed, and as far as I can see not available for Ubuntu 16.04.
Do you have any suggestion for solving this, other than upgrading (which
I would avoid for the time being)? Sorry, as I already mentioned it is
my first contribution to a bug report.

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

Title:
  my laptop freezes at the login screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I apologise in advance, this is my first report, therefore I am not sure if 
everything has been automatically collected, or if I need to provide further 
information than a short explanation of the problem.
   
  After updating the kernel at 4.4.0-128 on Ubuntu 16.04, first I had massive 
problems with the sound drivers. Then they disappeared (by themselves I would 
say, I had many tests but I don't think I screwed up anything serious) and, 
instead, now my sistem freezes at login screen. Sometimes it gives me the 
message that the wireless has been found. The mouse is available but I cannot 
interact with the screen, and also the clock is frozen. I have to brutally 
switch off the laptop for rebooting. A further kernel update to 4.4.0-130 
didn't help, either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luigi  2426 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul  3 17:31:25 2018
  HibernationDevice: RESUME=UUID=c24386f7-c59c-494d-b58d-abced7cc343c
  InstallationDate: Installed on 2017-02-28 (489 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 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 174f:2408 Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80TV
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed 
root=UUID=e98922f5-e948-421c-8d5f-2d7e1ad4dfe1 ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN23WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Torronto 5C2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN23WW:bd11/10/2016:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
  dmi.product.name: 80TV
  dmi.product.version: Lenovo ideapad 310-15IKB
  dmi.sys.vendor: LENOVO

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

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

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

Title:
  linux-gcp: 4.15.0-1012.12~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow 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 Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780124/+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 1780155] Status changed to Confirmed

2018-07-04 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  [regression] Ubuntu boots very slowly after kernel upgrading

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Ubuntu VM started to boot very slowly immediately after it has been
  upgraded to linux 4.15.0-24. So it seems it is a regression. With
  4.15.0-23 it boots normally.

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

  ~$ cat /proc/version_signature
  Ubuntu 4.15.0-24.26-generic 4.15.18

  ~$ systemd-analyze blame
     11min 41.457s plymouth-quit-wait.service
    5.684s srv1cv83.service
    1.601s networkd-dispatcher.service
    1.491s NetworkManager.service
    1.336s udisks2.service
    1.295s ModemManager.service
    1.255s accounts-daemon.service
    1.121s thermald.service
    1.082s grub-common.service

  ~$ systemd-analyze critical-chain
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  graphical.target @11min 43.954s
  └─multi-user.target @11min 43.954s
    └─anacron.service @8min 58.982s
  └─basic.target @912ms
    └─paths.target @912ms
  └─cups.path @912ms
    └─sysinit.target @909ms
  └─apparmor.service @471ms +438ms
    └─local-fs.target @462ms
  └─run-user-1001-gvfs.mount @11min 24.915s
    └─run-user-1001.mount @3.021s
  └─swap.target @395ms
    
└─dev-disk-by\x2duuid-82c9d942\x2d61f4\x2d42fc\x2dbddc\x2dfdb02217509d.swap 
@378ms +16ms
  
└─dev-disk-by\x2duuid-82c9d942\x2d61f4\x2d42fc\x2dbddc\x2dfdb02217509d.device 
@378ms

  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.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  accountant   1136 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  4 23:17:49 2018
  HibernationDevice: RESUME=UUID=82c9d942-61f4-42fc-bddc-fdb02217509d
  InstallationDate: Installed on 2018-06-05 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-24-generic 
root=UUID=959b7c8f-048c-4d32-b999-f00713e22153 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  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:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-2.11
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.11:cvnQEMU:ct1:cvrpc-q35-2.11:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-2.11
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780155/+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 1780155] [NEW] [regression] Ubuntu boots very slowly after kernel upgrading

2018-07-04 Thread Gannet

Public bug reported:

My Ubuntu VM started to boot very slowly immediately after it has been
upgraded to linux 4.15.0-24. So it seems it is a regression. With
4.15.0-23 it boots normally.

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

~$ cat /proc/version_signature
Ubuntu 4.15.0-24.26-generic 4.15.18

~$ systemd-analyze blame
   11min 41.457s plymouth-quit-wait.service
  5.684s srv1cv83.service
  1.601s networkd-dispatcher.service
  1.491s NetworkManager.service
  1.336s udisks2.service
  1.295s ModemManager.service
  1.255s accounts-daemon.service
  1.121s thermald.service
  1.082s grub-common.service

~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @11min 43.954s
└─multi-user.target @11min 43.954s
  └─anacron.service @8min 58.982s
└─basic.target @912ms
  └─paths.target @912ms
└─cups.path @912ms
  └─sysinit.target @909ms
└─apparmor.service @471ms +438ms
  └─local-fs.target @462ms
└─run-user-1001-gvfs.mount @11min 24.915s
  └─run-user-1001.mount @3.021s
└─swap.target @395ms
  
└─dev-disk-by\x2duuid-82c9d942\x2d61f4\x2d42fc\x2dbddc\x2dfdb02217509d.swap 
@378ms +16ms

└─dev-disk-by\x2duuid-82c9d942\x2d61f4\x2d42fc\x2dbddc\x2dfdb02217509d.device 
@378ms

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.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  accountant   1136 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  4 23:17:49 2018
HibernationDevice: RESUME=UUID=82c9d942-61f4-42fc-bddc-fdb02217509d
InstallationDate: Installed on 2018-06-05 (29 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
 lono wireless extensions.

 enp1s0no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-24-generic 
root=UUID=959b7c8f-048c-4d32-b999-f00713e22153 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
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:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:

dmi.bios.date: 02/06/2015
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-2.11
dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.11:cvnQEMU:ct1:cvrpc-q35-2.11:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-2.11
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug bionic

** Description changed:

- Ubuntu started to boot very slowly immediately after it has been
+ My Ubuntu VM started to boot very slowly immediately after it has been
  upgraded to linux 4.15.0-24. So it seems it is a regression. With
  4.15.0-23 it boots normally.
  
  ~$ uname -a
  Linux 1C-Q35 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  
  ~$ cat /proc/version_signature
  Ubuntu 4.15.0-24.26-generic 4.15.18
  
  ~$ systemd-analyze blame
-11min 41.457s plymouth-quit-wait.service
-   5.684s srv1cv83.service
-   1.601s networkd-dispatcher.service
-   1.491s NetworkManager.service
-   1.336s udisks2.service
-   1.295s ModemManager.service
-   1.255s accounts-daemon.service
-   1.121s thermald.service
-   1.082s grub-common.service
+    11min 41.457s plymouth-quit-wait.service
+   5.684s srv1cv83.service
+   1.601s networkd-dispatcher.service
+   1.491s NetworkManager.service
+   1.336s udisks2.service
+   1.295s ModemManager.service
+   1.255s accounts-daemon.service
+   1.121s thermald.service
+   1.082s grub-common.service
  
- 
- ~$ systemd-analyze critical-chain 
+ ~$ systemd-analyze critical-chain
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+"

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-07-04 Thread Chris U.

Also affected: Dell XPS 13 9345 Developer Edition.
The fix works for me, but what are inexperienced users going to do?

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-edge source package in Xenial:
Fix Released
Status in linux-oem source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released

Bug description:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

1. Boot into Ubuntu
2. Download
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
3. Install the downloaded package:
$ sudo dpkg -i
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
4. Make sure the kernel is installed without any error. Once installed,
reboot.
5. At grub, choose the newly installed kernel. You can choose the "recovery"
mode.
6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
7. In case your BIOS is not recovered, reboot to the new kernel, then reboot
*once again* to the new kernel, do not enter BIOS settings before the reboot.
After the second reboot, check BIOS.
8. If your BIOS issue remains, download another kernel from
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
and use dpkg to install it, then repeat steps 4 to 6.

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-30
Lenovo G50-70
Lenovo G50-80
Lenovo S20-30
Lenovo U31-70
Lenovo Y50-70
Lenovo Y70-70
Lenovo Yoga Thinkpad (20C0)
Lenovo Yoga 2 11" - 20332
Lenovo Yoga 3 11"
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Toshiba Satellite L70-A-13M
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw, 0xef6015
w25q32dw, 0xef6016
w25q64dw, 0xef6017
w25q128fw, 0xef6018

---

Original Description:

Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.

It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.

Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.

Lenovo forums at the moment are full of topics regading this issue.

Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1780124] Re: linux-gcp: 4.15.0-1012.12~16.04.1 -proposed tracker

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1012.12~16.04.1 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux-gcp: 4.15.0-1012.12~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow 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:
  New
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 Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780124/+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 1773993] Re: Mouse cursor having a longer trail, lagging and stuttering

2018-07-04 Thread Wont Tell

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1773993

Title:
  Mouse cursor having a longer trail, lagging and stuttering

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Xubuntu 16.04.4, Kernel: 4.13.0-44 x86_64, CPU: i3-4030U, Graphics:
  Intel HD 4400.

  After kernel 4.13.0-40, my mouse cursor started to have a bigger trail
  then before, lagging and stutter during some load. During loading
  redhift mouse experience more lag.

  On a kernel 4.13.0-39 and 4.13.0-41 all good.

  I've tried to test on a various kernels and here are the results:
  Xubuntu 16.04.4, Kernel 4.13.0-39 = Good
  Xubuntu 16.04.4, Kernel 4.13.0-40 = Bad
  Xubuntu 16.04.4, Kernel 4.13.0-41 = Good
  Xubuntu 16.04.4, Kernel 4.13.0-42 = Bad
  Xubuntu 16.04.4, Kernel 4.13.0-43 = Bad
  Xubuntu 16.04.4, Kernel 4.13.0-44 = Bad
  Xubuntu 16.04.4, Kernel 4.15.18(Ubuntu mainline) = Bad
  Xubuntu 16.04.4, Kernel 4.16.4(Ubuntu mainline) = Bad
  Ubuntu 18.04, Kernel 4.15 = Bad
  Xubuntu 18.04, Kernel 4.16.10(Ubuntu mainline) = Bad
  Xubuntu 18.04, Kernel 4.16.11(Ubuntu mainline) = Bad
  Xubuntu 18.04, Kernel 4.16.12(Ubuntu mainline) = Bad
  Fedora 28, Kernel 4.16.3 = Bad
  OpenSuse Tumbleweed, Kernel 4.16.8 = Good
  Manjaro 17.1.9 KDE, Kernel 4.9.96 = Good
  Manjaro 17.1.9 KDE, Kernel 4.14.36 = Good
  Manjaro 17.1.9 KDE, Kernel 4.16.4 = Good
  Manjaro 17.1.9 KDE, Kernel 4.17.0-1 = Good

  Please request any information and tests that may help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-44-generic 4.13.0-44.49~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-44.49~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-44-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 29 17:03:15 2018
  InstallationDate: Installed on 2017-07-23 (310 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Beta amd64 (20170723)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   user   2320 F...m pulseaudio
   /dev/snd/controlC1:  user   2320 F pulseaudio
   /dev/snd/controlC0:  user   2320 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d969d8ec-87e0-493c-b317-4e68535c1b21
  InstallationDate: Installed on 2017-07-23 (310 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Beta amd64 (20170723)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-44-generic.efi.signed 
root=UUID=2bf2a7b1-cc88-4a21-aaca-251f52e78964 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-44.49~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-44-generic N/A
   linux-backports-modules-4.13.0-44-generic  N/A
   linux-firmware 1.157.19
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 77.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227D:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

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

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

Title:
  linux-gcp: 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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780118/+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 1779457] Re: Laptop won't respond after suspend

2018-07-04 Thread Dominic White

Thanks, installed kernel 4.18[0] rc3 and that seems to have fixed the
problem so far.

With regards to your question about whether it was caused by a kernel
update, I'm not sure: the computer is relatively new, and I first
noticed the issue soon after getting it. If it's helpful, the kernel
versions I went through during that time are: 4.15.0-20 - 4.15.0-23.

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779457/+attachment/5158083/+files/WifiSyslog.txt

** Tags added: kernel-fixed-upstream

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

Title:
  Laptop won't respond after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.04 on a Lenovo Ideapad 320. After suspending and
  resuming, the screen wakes up as a mass of large blocks (several
  pixels across). There is no recognizable pattern to these pixels, but
  they do have the Ubuntu color palette...

  The computer is unresponsive to keyboard or mouse, and the only
  solution I currently have is to do a forced restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  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/controlC1:  dominic1901 F pulseaudio
   /dev/snd/controlC0:  dominic1901 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 30 07:47:41 2018
  InstallationDate: Installed on 2018-05-31 (30 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 80XS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=44f8fdb5-10cf-4907-92b2-0282c6c49acc ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN20WW:bd11/29/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.version: Lenovo ideapad 320-15ABR
  dmi.sys.vendor: LENOVO

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

** Summary changed:

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux-gcp: 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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
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:
  New
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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780118/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Michal Maleszka

** Changed in: linux (Ubuntu Bionic)
   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/1779827

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 19:31 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 --
  kernel-stable-master-bug: 1780112
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 04. July 2018 19:31 UTC
+ phase: Uploaded

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

Title:
  linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780120/+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

2018-07-04 Thread Dmitriy

** 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 1779974] Re: install bcmwl-kernel-source , Module wl not found in directory /lib/modules/4.15.0-24-generic

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

Title:
  install bcmwl-kernel-source , Module wl not found in directory
  /lib/modules/4.15.0-24-generic

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  sudo apt-get --reinstall install bcmwl-kernel-source
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/1,544 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 355817 files and directories currently installed.)
  Preparing to unpack 
.../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.2_amd64.deb ...
  Removing all DKMS Modules
  Done.
  Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.2) over 
(6.30.223.271+bdcom-0ubuntu1~1.2) ...
  Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.2) ...
  Loading new bcmwl-6.30.223.271+bdcom DKMS files...
  Building only for 4.15.0-24-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-24-generic
  Error! Bad return status for module build on kernel: 4.15.0-24-generic 
(x86_64)
  Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
information.
  modprobe: FATAL: Module wl not found in directory 
/lib/modules/4.15.0-24-generic
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic

  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.15.0-24-generic 
(x86_64)
  2018年 07月 04日 星期三 09:32:50 CST
  make: Entering directory '/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 *);
  ^
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’

[Kernel-packages] [Bug 1779899] Re: Wake-on-LAN stopped working with 4.15.0-24 kernel

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Wake-on-LAN stopped working with 4.15.0-24 kernel

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Wake-on-LAN had been working fine since Bionic installed.  When kernel
  4.15.0-24 was pushed out and installed, it quit working.  Set system
  to boot from 4.15.0-23, and it works again.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bill   1741 F pulseaudio
   /dev/snd/controlC0:  bill   1741 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Jul  3 11:14:09 2018
  HibernationDevice: RESUME=UUID=adc97911-6d93-4094-8ec4-15cab05377e7
  InstallationDate: Installed on 2018-04-27 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=0ca22edb-e6b0-412b-ad6e-00b2126b37c7 ro quiet splash vt.handoff=1
  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:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779899/+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 1780103] Re: Network namespaces support for non-IP suddenly missing

2018-07-04 Thread KJH

I can confirm that the 4.4.0-128-generic kernel does *not* have the
problem, while the 4.4.0-130-generic kernel *does*.

Op wo 4 jul. 2018 om 17:21 schreef Daniel Manrique <
daniel.manri...@canonical.com>:

> Hello,
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
>
> As diagnostic procedures, I can suggest:
>
> You could try rebooting, hitting the key to get the grub menu (Shift,
> see https://askubuntu.com/questions/16042/how-to-get-to-the-grub-menu-
> at-boot-time
> )
> and choosing the previous kernel, to see if that fixes the
> issue you're seeing. If so, it might well be related to the kernel
> upgrade.
>
> Then, /var/log/apt/history.log will tell you exactly what (and when) was
> upgraded.
>
> That said, The problem as you reported is not related to the Canonical
> SSO provider or service. I'll move it to the "Linux" package, since per
> your description it seems to correlate with a kernel upgrade. Note that
> you will be required to provide more debugging information as per the
> kernel debugging procedures.
>
> https://wiki.ubuntu.com/Kernel/Debugging/Symptom
>
>
> ** Project changed: canonical-identity-provider => linux (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1780103
>
> Title:
>   Network namespaces support for non-IP suddenly missing
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   I run 16.04, and I keep daily track of all dist-upgrades. Yesterday (3
>   july 2018) there was an upgrade, and it must have been a kernel
>   upgrade, because my machine had rebooted (which I make it do
>   automatically if needed).
>
>   From today, the system tests on my project have stopped working (C
>   development). These system tests do the following: using the 'ip'
>   command, they set up several network namespaces, in which I run
>   several executables concurrently, that exchange network messages with
>   each other. The namespaces that use IP have kept on working, while the
>   ones that don't (I'm implementing an ethernet network packet structure
>   of my own) have stopped working. I've done the same tests on my
>   laptop, which is also a 16.04, on which I haven't done the upgrade
>   (and I'm very hesitant to do so now, because this is my bread and
>   butter), and there they work still.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780103/+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/1780103

Title:
  Network namespaces support for non-IP suddenly missing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I run 16.04, and I keep daily track of all dist-upgrades. Yesterday (3
  july 2018) there was an upgrade, and it must have been a kernel
  upgrade, because my machine had rebooted (which I make it do
  automatically if needed).

  From today, the system tests on my project have stopped working (C
  development). These system tests do the following: using the 'ip'
  command, they set up several network namespaces, in which I run
  several executables concurrently, that exchange network messages with
  each other. The namespaces that use IP have kept on working, while the
  ones that don't (I'm implementing an ethernet network packet structure
  of my own) have stopped working. I've done the same tests on my
  laptop, which is also a 16.04, on which I haven't done the upgrade
  (and I'm very hesitant to do so now, because this is my bread and
  butter), and there they work still.

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 18:33 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 --
  kernel-stable-master-bug: 1780112
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 04. July 2018 18:33 UTC
+ phase: Uploaded

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

Title:
  linux-azure: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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 --
  kernel-stable-master-bug: 1780112
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780117/+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 1780120] Re: linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

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

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

Title:
  linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780120/+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 1780120] Re: linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux-azure: 4.15.0-1016.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging

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

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

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

Title:
  linux-azure: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780117/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Sorry for the late reply.

Can you make sure hibernation was affected by commit
a192aa923b66a435aae56983c4912ee150bc9b32?

Please do the following:

$ git checkout a192aa923b66a435aae56983c4912ee150bc9b32
...then build and try the kernel

$ git checkout a192aa923b66a435aae56983c4912ee150bc9b32^
...then build and try the kernel without the commit

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Kubuntu 18.04 on 3 different machines (my friend's
  and my own) with no suspend problems but my HP Pavilion 11 x360 does
  not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  
  Correct behaviour is - 

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  
  What happens - 

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  
  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  
  Checking the logs suggests that the machine believes it is in suspend mode 
sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na 
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

2018-07-04 Thread Kalpana S Shetty

We have used below bionic "-proposed" path to get install it freshly,
still it fails to boot.

Issue is still observed after installing from http://ports.ubuntu.com
/ubuntu-ports/dists/bionic-proposed/main/installer-
ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

Please advice with the right path to pick the fixed kernel.

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

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

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

Bug description:
  Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot
  with 4.15.0-22-generic and is in a reboot cycle.

  ```
  Exiting petitboot. Type 'exit' to return.
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1
  [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2
  [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec
  [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1]
  [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV
  [2.660462] Modules linked in:
  [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic 
#24-Ubuntu
  [2.660549] NIP:  c000b9ec LR:  CTR: 

  [2.660603] REGS: c0003fd0bd40 TRAP: 0300   Not tainted  
(4.15.0-22-generic)
  [2.660657] MSR:  90001031   CR:   XER: 

  [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 
SOFTE: -4611686018408771536 
  [2.660713] GPR00:  7fffcd511100  
 
  [2.660713] GPR04:    
 
  [2.660713] GPR08:    
 
  [2.660713] GPR12: 75501b231700 000200f0  
 
  [2.660713] GPR16:    
 
  [2.660713] GPR20:    
 
  [2.660713] GPR24:    
 
  [2.660713] GPR28:    
 
  [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [2.661249] LR []   (null)
  [2.661285] Call Trace:
  [2.661303] Instruction dump:
  [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090 
  [2.661387] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 4810 
  [2.661445] ---[ end trace b607b09fe6490607 ]---
  […]
  ```

  Please find the full log attached. Selecting Linux 4.4.0-124-generic
  works.

  ```
  $ uname -a
  Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP 
Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
  $ dpkg -l linux-image-4.15.0-22-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version
Architecture   Description
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 23 16:40 seq
   crw-rw 1 root audio 116, 33 May 23 16:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory:

[Kernel-packages] [Bug 1780117] Re: linux-azure: 4.15.0-1016.16 -proposed tracker

** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.15.0-1016.16 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux-azure: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780117/+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 1779413] Re: Bluetooth bug

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

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

Title:
  Bluetooth bug

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good afternoon!
  I have a small problem. It is connected with the mouse from Microsoft (BTLE 
Precision Mouse). She does not want to connect on bluetooth. The version of my 
bluetooth 4.1.
  Ubuntu 4.15.0-22.24-generic 4.15.17

  ```
  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  ```

  Here's the output when trying to pair:
  ```
  pair E0:52:31:92:AB:5B
  Attempting to pair with E0:52:31:92:AB:5B
  [CHG] Device E0:52:31:92:AB:5B Connected: yes
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
  [NEW] Primary Service
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009
180a--1000-8000-00805f9b34fb
Device Information
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000c
2a24--1000-8000-00805f9b34fb
Model Number String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0010
2a28--1000-8000-00805f9b34fb
Software Revision String
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0012
2a50--1000-8000-00805f9b34fb
PnP ID
  [NEW] Characteristic
/org/bluez/hci0/dev_E0_52_31_92_AB_5B/service0009/char0014
6ff6f99d-536c-4ea6-88a3-c3aabb718b68
Vendor specific
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1800--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1801--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180a--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 180f--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1812--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B UUIDs: 1813--1000-8000-00805f9b34fb
  [CHG] Device E0:52:31:92:AB:5B ServicesResolved: yes
  [CHG] Device E0:52:31:92:AB:5B Modalias: usb:v045Ep0821d0105
  Failed to pair: org.freedesktop.DBus.Error.NoReply
  ```

  journalctl -u bluetooth
  ```
  июн 29 23:42:34 mi bluetoothd[5983]: No cache for E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:35 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:40 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:41 mi bluetoothd[5983]: bt_uhid_send: Invalid argument (22)
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to register device interface for 
E0:52:31:92:AB:5B
  июн 29 23:42:45 mi bluetoothd[5983]: Unable to get device object for 
E0:52:31:92:AB:5B

  ```
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pocoz  2614 F...m pulseaudio
   /dev/snd/controlC0:  pocoz  2614 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04

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

2018-07-04 Thread Ubuntu Kernel Bot

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

apport-collect 1780137

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

Title:
  [Regression] EXT4-fs error (device sda1):
  ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
  certification suite. Platform is a HiSilicon D05 arm64 server, but we
  don't have reason to believe it is platform specific at this time.

  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr
  to 524288).

  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.

  I bisected this down to the following commit:

  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500

  ext4: don't update checksum of new initialized bitmaps
  
  BugLink: http://bugs.launchpad.net/bugs/1773233
  
  commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 17:00 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 --
  kernel-stable-master-bug: 1780112
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Wednesday, 04. July 2018 17:00 UTC
+ phase: Packaging

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

Title:
  linux-gcp:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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:
  New
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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780118/+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 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker

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

** This bug is no longer a duplicate of bug 1778772
   linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker
** This bug has been marked a duplicate of bug 1779367
   linux-gcp:  -proposed tracker

** This bug is no longer a duplicate of bug 1779367
   linux-gcp:  -proposed tracker
** This bug has been marked a duplicate of bug 1780124
   linux-gcp:  -proposed tracker

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1780124
   linux-gcp:  -proposed tracker

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

Title:
  linux-gcp:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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:
  New
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 Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779367/+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 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

2018-07-04 Thread voidvector

Appears to also effect Ubuntu Desktop with crng_init enabled.

* EC2 instances - effected, same problem as described
* Home Desktop (Xubuntu) - effected, see description below
* Home Server (Lubuntu that has crng_init=0 for some reason) - uneffected

cloud-init might just be a red-herring, as my Home Desktop would hang
for 30+ seconds on "docker.service". When I disable Docker, it would
still hang for 30 seconds, but "systemd-analyze blame" won't provide any
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/1780062

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in cloud-init source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+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 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

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

** Changed in: cloud-init (Ubuntu Bionic)
   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/1780062

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in cloud-init source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+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 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

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

** Changed in: cloud-init (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/1780062

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in cloud-init source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+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 1780137] [NEW] [Regression] EXT4-fs error (device sda1): ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

2018-07-04 Thread dann frazier

Public bug reported:

We're seeing a very reproducible regression in the bionic kernel
triggered by the stress-ng chdir test performed by the Ubuntu
certification suite. Platform is a HiSilicon D05 arm64 server, but we
don't have reason to believe it is platform specific at this time.

[Test Case]
$ sudo apt-add-repository -y ppa:hardware-certification/public
$ sudo apt install -y canonical-certification-server
$ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
$ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

This test runs a series of stress-ng tests against /dev/sda, and fails
on the "chdir" test. To speed up reproduction, reduce the test list to
just "chdir" in the disk_stress_ng script. Attempts to reproduce this
directly with stress-ng have failed - presumably because of other
environment setup that this script performs (e.g. setting aio-max-nr to
524288).

Our reproduction test is to use a non-root disk because it can lead to
corruption, and mkfs.ext4'ing the partition just before running the
test, to get to a pristine fs state.

I bisected this down to the following commit:

commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
Author: Theodore Ts'o 
Date:   Mon Feb 19 14:16:47 2018 -0500

ext4: don't update checksum of new initialized bitmaps

BugLink: http://bugs.launchpad.net/bugs/1773233

commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

Title:
  [Regression] EXT4-fs error (device sda1):
  ext4_validate_inode_bitmap:99: comm stress-ng: Corrupt inode bitmap

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We're seeing a very reproducible regression in the bionic kernel
  triggered by the stress-ng chdir test performed by the Ubuntu
  certification suite. Platform is a HiSilicon D05 arm64 server, but we
  don't have reason to believe it is platform specific at this time.

  [Test Case]
  $ sudo apt-add-repository -y ppa:hardware-certification/public
  $ sudo apt install -y canonical-certification-server
  $ sudo mkfs.ext4 /dev/sda1 (Obviously, this should not be your root disk!!)
  $ sudo /usr/lib/plainbox-provider-checkbox/bin/disk_stress_ng sda --base-time 
240 --really-run

  This test runs a series of stress-ng tests against /dev/sda, and fails
  on the "chdir" test. To speed up reproduction, reduce the test list to
  just "chdir" in the disk_stress_ng script. Attempts to reproduce this
  directly with stress-ng have failed - presumably because of other
  environment setup that this script performs (e.g. setting aio-max-nr
  to 524288).

  Our reproduction test is to use a non-root disk because it can lead to
  corruption, and mkfs.ext4'ing the partition just before running the
  test, to get to a pristine fs state.

  I bisected this down to the following commit:

  commit 555bc9b1421f10d94a1192c7eea4a59faca3e711
  Author: Theodore Ts'o 
  Date:   Mon Feb 19 14:16:47 2018 -0500

  ext4: don't update checksum of new initialized bitmaps
  
  BugLink: http://bugs.launchpad.net/bugs/1773233
  
  commit 044e6e3d74a3d7103a0c8a9305dfd94d64000660 upstream.

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 16:36 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
- kernel-stable-phase-changed:Wednesday, 04. July 2018 16:36 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-azure:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780117/+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 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk

2018-07-04 Thread Bug Watch Updater

Launchpad has imported 129 comments from the remote bug at
https://bugzilla.novell.com/show_bug.cgi?id=425480.

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


On 2008-09-11T13:05:40+00:00 Stbinner wrote:

Updated today my work station after two or three weeks to current
Factory kernel and since then the onboard network card doesn't show up
anymore:

 e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k2
 e1000e: Copyright (c) 1999-2008 Intel Corporation.
 e1000e :00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
 e1000e :00:19.0: setting latency timer to 64
 input: PC Speaker as /devices/platform/pcspkr/input/input3
 :00:19.0: :00:19.0: The NVM Checksum Is Not Valid
 e1000e :00:19.0: PCI INT A disabled
 e1000e: probe of :00:19.0 failed with error -5

Booted an openSUSE 11.0 installation and same issue there now too. Some
BIOS/checksum got broken?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/10


On 2008-09-11T13:06:33+00:00 Stbinner wrote:

Created attachment 239061
dmesg of Factory installation

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


On 2008-09-11T13:07:04+00:00 Stbinner wrote:

Created attachment 239062
dmesg of 11.0 installation

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


On 2008-09-21T15:25:56+00:00 Stbinner wrote:

*** Bug 428180 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/20


On 2008-09-21T16:29:54+00:00 Karsten-keil wrote:

Intel did cleanup e1000 and e1000e to have no duplicate PCI IDs in both 
drivers. Maybe they removed this on the wrong driver.
Can you please try to unload e1000e and load e1000 manually if the card is not 
detected, then please add the ids to the driver on runtime:

echo "vendor device subvendor subdevice class class_mask driver_data" > \
/sys/bus/pci/drivers/e1000/new_id

All fields are passed in as hexadecimal values (no leading 0x).
The vendor and device fields are mandatory, the others are optional.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/21


On 2008-09-21T17:26:30+00:00 Andreas Jaeger wrote:

See bug 428180 - I can load the e1000 just fine but it does not work at
all.

after:  echo "8086 104b" > /sys/bus/pci/drivers/e1000/new_id

I see the following in dmesg:
e1000 :00:19.0: setting latency timer to 64
e1000: :00:19.0: e1000_probe: The EEPROM Checksum Is Not Valid
/*/
Current EEPROM Checksum : 0x
Calculated  : 0xbaf9
OffsetValues
  ==
: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
0010: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
0020: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
0030: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
0040: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
0050: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
0060: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
0070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
Include this output when contacting your support provider.
This is not a software error! Something bad happened to your hardware or
EEPROM image. Ignoring this problem could result in further problems,
possibly loss of data, corruption or system hangs!
The MAC Address will be reset to 00:00:00:00:00:00, which is invalid
and requires you to set the proper MAC address manually before continuing
to enable this network device.
Please inspect the EEPROM dump and report the issue to your hardware vendor
or Intel Customer Support.
/*/
e1000: :00:19.0: e1000_probe: Invalid MAC Address
e1000: :00:19.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 
00:00:00:00:00:00
e1000: :00:19.0: e1000_probe: This device (id 8086:104b) will no longer be 
supported by this driver i
n the future.
e1000: :00:19.0: e1000_probe: please use the "e1000e" driver instead.
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection


Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555/comments/22


On 2008-09-21T18:31:10+00:00 Karsten-keil wrote:

I fear that the EEPROM was deleted. This may be the reason, the fix is e1000 
related, but it seems that e1000e has

[Kernel-packages] [Bug 1371379] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5139 Card Reader Controller doesn't load

2018-07-04 Thread Bug Watch Updater

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.novell.com/show_bug.cgi?id=890096.

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


On 2014-08-03T02:09:24+00:00 Marcel Witte wrote:

User-Agent:   Mozilla/5.0 (X11; Linux x86_64; rv:32.0)
Gecko/20100101 Firefox/32.0

I use an ASUS N550JV. After updating from 13.1 to Factory, the card
reader in not detected anymore. The driver now moved to rtsx_usb module
and that is not loaded automatically. After modprobe rtsx_usb the card
reader is working again.

lsusb:

Bus 003 Device 005: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card 
Reader Controller
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass   255 Vendor Specific Subclass
  bDeviceProtocol   255 Vendor Specific Protocol
  bMaxPacketSize064
  idVendor   0x0bda Realtek Semiconductor Corp.
  idProduct  0x0139 RTS5139 Card Reader Controller
  bcdDevice   39.60
  iManufacturer   1 Generic
  iProduct2 USB2.0-CRW
  iSerial 3 2010020139600
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   39
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  4 CARD READER
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass  6 
  bInterfaceProtocol 80 
  iInterface  5 Bulk-In, Bulk-Out, Interface
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0003  1x 3 bytes
bInterval  10
Device Qualifier (for other device speed):
  bLength10
  bDescriptorType 6
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  bNumConfigurations  1
Device Status: 0x
  (Bus Powered)

Reproducible: Always

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


On 2014-08-08T21:09:11+00:00 Jeffm-9 wrote:

This might be a bug in depmod. The device IDs are in the driver (which
is how it actually loads when you modprobe it) but they're not getting
picked up for modules.alias, which is what gets used for autoloading.

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


On 2014-08-08T21:23:39+00:00 Jeffm-9 wrote:

Actually, no, it's much simpler. It's just not publishing its device
table.

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


On 2014-08-08T21:32:20+00:00 Jeffm-9 wrote:

Created attachment 601759
rtsx_usb: export device table

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


On 2014-08-08T21:32:55+00:00 Jeffm-9 wrote:

This patch has been committed to the git master branch.

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


** Changed in: linux (openSUSE)
   Status: Unknown => Fix

[Kernel-packages] [Bug 315977] Re: PATCH: Quirk to pickup correct alsa mixer profile on HP 6730b

2018-07-04 Thread Bug Watch Updater

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.novell.com/show_bug.cgi?id=457909.

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

On 2008-12-10T09:07:31+00:00 Hartmut-sbosny wrote:

I use a laptop HP 6730B with intel sound chipset 82801I. Afer installation
I had no sound, neither in 11.0 nor in 11.1 RC1. In 11.1 I could overcome the 
problem via the menu "Yast ==> hardware ==> sound" by setting the 'model' 
option to "laptop" (accord. to a tip in 
http://www.linlap.com/wiki/HP-Compaq+6730B, where was proposed to add/change in 
/etc/modprobe.conf the line “options snd-hda-intel model=laptop”; the SUSE 
equivalent should be the file 
/etc/modprobe.d/sound, but in 11.0 this didn't help.)

This is the content of /etc/modprobe.d/sound after my above change via
yast.

options snd-hda-intel model=laptop
options snd slots=snd-hda-intel
# u1Nb.5BNmHXMrXg9:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel

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

On 2008-12-10T09:21:23+00:00 Tiwai-r wrote:

Could you run /usr/sbin/alsa-info.sh with --no-upload option, and attach
the generated file?

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

On 2008-12-10T09:33:44+00:00 Hartmut-sbosny wrote:

Created attachment 259123
output of "alsa-info.sh --no-upload" (after my yast setting)

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

On 2008-12-10T09:35:48+00:00 Hartmut-sbosny wrote:

(In reply to comment #1 from Takashi Iwai)
> Could you run /usr/sbin/alsa-info.sh with --no-upload option, and attach the
> generated file?
> 

I sent is already with my first report, but anyhow it got lost. I try it
again

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

On 2008-12-10T09:57:14+00:00 Tiwai-r wrote:

Thanks.  I fixed now on both ALSA git tree and SUSE kernel tree.
The next update-kernel should work without model option.

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

On 2008-12-10T10:16:03+00:00 Hartmut-sbosny wrote:

Created attachment 259129
output of "alsa-info.sh --no-upload" for the yast default settings

Because my sent alsa-info.sh output looks correct after my yast settings, 
I reset (to verify the bug) in "yast ==> hardware ==> sound" the default 
settings,
and run alsa-info.sh again. The term "model=laptop" is now missing.
Also in /etc/modprobe.d/sound, which looks now so:

  options snd slots=snd-hda-intel
  # u1Nb.5BNmHXMrXg9:82801I (ICH9 Family) HD Audio Controller
  alias snd-card-0 snd-hda-intel

And the sound is gone.

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

On 2008-12-10T10:20:38+00:00 Hartmut-sbosny wrote:

(In reply to comment #4 from Takashi Iwai)
> Thanks.  I fixed now on both ALSA git tree and SUSE kernel tree.
> The next update-kernel should work without model option.
> 

Wow, that's fast! Thanks, and my last post was too slow. :-)

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

On 2009-02-26T14:32:57+00:00 Swamp-a wrote:

Update released for: kernel-debug, kernel-debug-base, kernel-debug-debuginfo, 
kernel-debug-debugsource, kernel-debug-extra, kernel-default, 
kernel-default-base, kernel-default-debuginfo, kernel-default-debugsource, 
kernel-default-extra, kernel-docs, kernel-kdump, kernel-kdump-debuginfo, 
kernel-kdump-debugsource, kernel-pae, kernel-pae-base, kernel-pae-extra, 
kernel-ppc64, kernel-ppc64-base, kernel-ppc64-debuginfo, 
kernel-ppc64-debugsource, kernel-ppc64-extra, kernel-ps3, kernel-ps3-debuginfo, 
kernel-ps3-debugsource, kernel-source, kernel-source-debuginfo, kernel-syms, 
kernel-trace, kernel-trace-base, kernel-trace-debuginfo, 
kernel-trace-debugsource, kernel-trace-extra, kernel-vanilla, 
kernel-vanilla-debuginfo, kernel-vanilla-debugsource, kernel-xen, 
kernel-xen-base, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-extra
Products:
openSUSE 11.1 (debug, i586, ppc, x86_64)

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

** Changed in: linux (openSUSE)
   Importance: Unknown => High

-- 
You

[Kernel-packages] [Bug 1780120] Re: linux-azure: -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 16:32 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
- kernel-stable-phase-changed:Wednesday, 04. July 2018 16:32 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-azure:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
+ kernel-stable-phase:Uploaded

** 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
  
  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.15.0-26.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-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-certification-testing 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:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)
  kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
- kernel-stable-phase-changed:Wednesday, 04. July 2018 16:31 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-aws:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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:
  New
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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 16:32 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
- kernel-stable-phase-changed:Wednesday, 04. July 2018 16:32 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-kvm:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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 --
  kernel-stable-master-bug: 1780112
  phase: Packaging

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
+ kernel-stable-phase-changed:Wednesday, 04. July 2018 16:33 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
- kernel-stable-phase-changed:Wednesday, 04. July 2018 16:33 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-gcp:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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:
  New
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 Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780124/+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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-07-04 Thread Robie Basak

Hello Ian, or anyone else affected,

Accepted bluez into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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-04 Thread toni.spets

Adding to the confusion here:

I'm running a Ryzen 1700 on Asus PRIME B350-PLUS motherboard and on BIOS
version 4011 I have the "Power Supply Idle Control" option and I have
changed it from "Auto" to "Low Current Idle" a week or so ago and after
that I have had zero lockups.

According to this bug report disabling C6 states *or* setting that
option to "Typical Current Idle" should work and "Auto" should mean "Low
Current Idle" hence it should not have made any difference. zenstates.py
shows C6 enabled for both package and core.

Unless the Ubuntu 18.04 kernel 4.15.0-*-generic got an off-tree patch
applied somewhere in-between my reboots I'm confused and relieved at the
same time.

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

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

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

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

** This bug has been marked a duplicate of bug 1779367
   linux-gcp:  -proposed tracker

** This bug is no longer a duplicate of bug 1779367
   linux-gcp:  -proposed tracker
** This bug has been marked a duplicate of bug 1780124
   linux-gcp:  -proposed tracker

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

Title:
  linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.15.0-1010.10~16.04.1 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: 1776333
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

** This bug has been marked a duplicate of bug 1780120
   linux-azure:  -proposed tracker

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

Title:
  linux-azure:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779364/+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 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

2018-07-04 Thread Pablo

How do you install test kernel?
I tried dpki -i linux-modules-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb 
linux-modules-extra-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb 
linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb

but I get error:

Preparing to unpack 
linux-modules-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb ...
Unpacking linux-modules-4.15.0-24-generic (4.15.0-24.26+crng4) over 
(4.15.0-24.26+crng4) ...
Preparing to unpack 
linux-modules-extra-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb ...
Unpacking linux-modules-extra-4.15.0-24-generic (4.15.0-24.26+crng4) over 
(4.15.0-24.26+crng4) ...
dpkg: regarding 
linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb containing 
linux-image-unsigned-4.15.0-24-generic:
 linux-image-unsigned-4.15.0-24-generic conflicts with 
linux-image-4.15.0-24-generic
  linux-image-4.15.0-24-generic (version 4.15.0-24.26) is present and installed.

dpkg: error processing archive 
linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb (--install):
 conflicting packages - not installing linux-image-unsigned-4.15.0-24-generic
Setting up linux-modules-4.15.0-24-generic (4.15.0-24.26+crng4) ...
Setting up linux-modules-extra-4.15.0-24-generic (4.15.0-24.26+crng4) ...
Processing triggers for linux-image-4.15.0-24-generic (4.15.0-24.26) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.15.0-24-generic
Found initrd image: /boot/initrd.img-4.15.0-24-generic
Found linux image: /boot/vmlinuz-4.15.0-23-generic
Found initrd image: /boot/initrd.img-4.15.0-23-generic
Found linux image: /boot/vmlinuz-4.15.0-22-generic
Found initrd image: /boot/initrd.img-4.15.0-22-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
Errors were encountered while processing:
 linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb


Or how do I revert to previous working kernel (I don't have grub installed... 
long story).

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

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

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1779827/+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 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels

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

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

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

Title:
  Cloud-init causes potentially huge boot delays with 4.15 kernels

Status in cloud-init package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in cloud-init source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")

  This causes cloud-init to stall for a potentially long time during
  boot (waiting for entropy I presume). Google reported boot delays of
  75 minutes.

  I've tracked this down to the following import in templater.py which causes 
the delay:
  from jinja2 import Template as JTemplate

  Which is called when cc_update_etc_hosts is imported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+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 1780114] Re: linux-oem: -proposed tracker

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

** This bug has been marked a duplicate of bug 1779357
   linux-oem:  -proposed tracker

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

Title:
  linux-oem:  -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1780112

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780114/+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 1777646] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1

2018-07-04 Thread Robie Basak

Does this package work correctly against the equivalent kernels in
Bionic and Cosmic please? Obviously they'd be different versions, but
I'd like to ensure the spirit of the SRU rule about being fixed in the
development release to avoid a regression where a user uses a particular
kernel flavor, upgrades, and gets a failure.

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe-
  edge 4.15.0-23.25~16.04.1

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

Bug description:
  [Impact]

  Currently the DKMS package fails to install on supported custom
  kernels that are based on 4.15. That includes the current 4.15
  hwe-edge and some of the custom and cloud kernels as well.

  [Test Case]

  Install the broadcom-sta package with the 4.15 hwe-edge kernel. The
  package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that, the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.13
  - linux-hwe-edge 4.15
  - linux-azure 4.15

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20180528_193622_1abd6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20180528_193842_1abd6@/log.gz

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

2018-07-04 Thread Dmitriy

kernel-bug-exists-upstream

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

2018-07-04 Thread Dmitriy

The problem occurred after the kernel was automatically updated to version 
4.16. This is not the first time when the kernel is updated, and I tried to 
reinstall bcmwl-kernel-sourse. It did not help, I tried other recipes on the 
net, but they also did not help.
On the previous kernels 4.15 4.13 everything worked, after updating and 
attempts to restore the work of the wifi, work only on version 4.4 of my 
installed.
With versions of the system above 4.16 there are complications they are not 
correctly installed due to the lack of the libssl1.1 module, with its 
installation there are problems.
The driver, on reinstallation, produces errors that can not be installed and 
there is no WL module
help me please

-- 
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
  --- 
  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 1779363] Re: linux-kvm: 4.15.0-1013.13 -proposed tracker

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

** This bug has been marked a duplicate of bug 1780119
   linux-kvm:  -proposed tracker

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

Title:
  linux-kvm: 4.15.0-1013.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

** This bug has been marked a duplicate of bug 1780117
   linux-azure:  -proposed tracker

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

Title:
  linux-azure: 4.15.0-1015.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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/1779360/+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 1779354] Re: linux: 4.15.0-25.27 -proposed tracker

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

** This bug has been marked a duplicate of bug 1780112
   linux:  -proposed tracker

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

Title:
  linux: 4.15.0-25.27 -proposed tracker

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

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

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

  backports: bug 1779364 (linux-azure), bug 1779366 (linux-azure-edge), bug 
1779367 (linux-gcp), bug 1779371 (linux-hwe), bug 1779372 (linux-hwe-edge)
  derivatives: bug 1779355 (linux-raspi2), bug 1779357 (linux-oem), bug 1779358 
(linux-aws), bug 1779360 (linux-azure), bug 1779361 (linux-gcp), bug 1779363 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

** 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
+ 
+ backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
+ derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)

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

Title:
  linux: 4.15.0-26.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-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-certification-testing 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:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)

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

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

** This bug has been marked a duplicate of bug 1780115
   linux-aws:  -proposed tracker

-- 
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:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

** This bug has been marked a duplicate of bug 1780118
   linux-gcp:  -proposed tracker

-- 
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:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.15.0-26.28 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 4.15.0-26.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-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-certification-testing 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:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: bug 1780120 (linux-azure), bug 1780122 (linux-azure-edge), bug 
1780124 (linux-gcp), bug 1780126 (linux-hwe), bug 1780128 (linux-hwe-edge)
  derivatives: bug 1780113 (linux-raspi2), bug 1780114 (linux-oem), bug 1780115 
(linux-aws), bug 1780117 (linux-azure), bug 1780118 (linux-gcp), bug 1780119 
(linux-kvm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1780112/+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 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels