[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13

[james guo]

Not sure how to add the tag: '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/1751990

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13

[james guo]

just additional attached file

** Attachment added: "IMG_20180404_124551.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990/+attachment/5100767/+files/IMG_20180404_124551.jpg

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13

[james guo]

log are produced by using kernel 4.8 since 4.13 will not boot, will not
be able to do anything,(do you want a log from 4.13 with cuda?)

tried 4.16, will not boot, attached are installation log and boot log
image.

** Attachment added: "install416.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990/+attachment/5100765/+files/install416.log

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1596866] Re: NMI watchdog: Watchdog detected hard LOCKUP on cpu 0 - Xenial - Python

[Michael Sherman]

I am experiencing this issue on a new xeon scalable machine.
I can confirm that it is present with xenial linux-image-generic, and 
linux-image-generic-hwe, kernels 4.4.0-116, and 4.13.0-38, and I can reproduce 
it at will.

It no longer seems to occur on kernel 4.15.0-13.

In all cases, clocksource was already set to TSC automatically on install.
The soft lockup and hard lockup were triggered each time by a waf build of the 
ns3 project.
In each case, a failure occurred while running the commands as a regular user, 
but the system was stable if run as root, or with sudo.


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

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

Title:
  NMI watchdog: Watchdog detected hard LOCKUP on cpu 0 - Xenial - Python

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am receiving quite regular hardlockups on python (27) in xenial:

  Linux rts-os-s-03 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  Ubuntu 16.04 LTS \n \l

  Python 27:
  ii  python   2.7.11-1
amd64interactive high-level object-oriented language (default version)
  ii  python2.72.7.11-7ubuntu1 
amd64Interactive high-level object-oriented language (version 2.7)

  Python 3:
  ii  python3  3.5.1-3 
amd64interactive high-level object-oriented language (default python3 
version)

  
  Jun 28 06:52:42  kernel: [ 1634.052991] NMI watchdog: Watchdog detected 
hard LOCKUP on cpu 0
  Jun 28 06:52:42  kernel: [ 1634.059516] Modules linked in: iptable_raw 
kvm_intel ebtable_filter ebtables ip6table_filter ip6_tables xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_tcpudp iptable_filter 
ip_tables x_tables veth bridge stp llc bonding dcdbas intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm irqbypass shpchp lpc_ich 
ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi openvswitch nf_defrag_ipv6 nf_conntrack autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd bnx2x ahci 
libahci tg3 megaraid_sas vxlan ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c [last unloaded: kvm_intel]
  Jun 28 06:52:42  kernel: [ 1634.059790] CPU: 0 PID: 52914 Comm: python 
Not tainted 4.4.0-28-generic #47-Ubuntu
  Jun 28 06:52:42  kernel: [ 1634.059791] Hardware name: Dell Inc. 
PowerEdge R730/0H21J3, BIOS 1.5.4 10/002/2015
  Jun 28 06:52:42  kernel: [ 1634.059792]  0086 
2732bfd7 887b254bbbd0 813eb1a3
  Jun 28 06:52:42  kernel: [ 1634.059794]   
 887b254bbbe8 8113b3bd
  Jun 28 06:52:42  kernel: [ 1634.059796]  887e4da1a000 
887b254bbc20 81183e4c 0001
  Jun 28 06:52:42  kernel: [ 1634.059797] Call Trace:
  Jun 28 06:52:42  kernel: [ 1634.059804]  [] 
dump_stack+0x63/0x90
  Jun 28 06:52:42  kernel: [ 1634.059807]  [] 
watchdog_overflow_callback+0xbd/0xd0
  Jun 28 06:52:42  kernel: [ 1634.059810]  [] 
__perf_event_overflow+0x8c/0x1d0
  Jun 28 06:52:42  kernel: [ 1634.059811]  [] 
perf_event_overflow+0x14/0x20
  Jun 28 06:52:42  kernel: [ 1634.059814]  [] 
intel_pmu_handle_irq+0x1e1/0x4a0
  Jun 28 06:52:42  kernel: [ 1634.059817]  [] ? 
__alloc_pages_nodemask+0x1b1/0xb60
  Jun 28 06:52:42  kernel: [ 1634.059821]  [] ? 
try_charge+0xd4/0x640
  Jun 28 06:52:42  kernel: [ 1634.059823]  [] ? 
mem_cgroup_try_charge+0x6b/0x1b0
  Jun 28 06:52:42  kernel: [ 1634.059826]  [] ? 
lru_cache_add_active_or_unevictable+0x27/0xa0
  Jun 28 06:52:42  kernel: [ 1634.059830]  [] ? 
handle_mm_fault+0xcaa/0x1820
  Jun 28 06:52:42  kernel: [ 1634.059831]  [] ? 
vma_merge+0x22e/0x330
  Jun 28 06:52:42  kernel: [ 1634.059834]  [] 
perf_event_nmi_handler+0x2d/0x50
  Jun 28 06:52:42  kernel: [ 1634.059837]  [] 
nmi_handle+0x69/0x120
  Jun 28 06:52:42  kernel: [ 1634.059839]  [] 
default_do_nmi+0x40/0x100
  Jun 28 06:52:42  kernel: [ 1634.059841]  [] 
do_nmi+0xe2/0x130
  Jun 28 06:52:42  kernel: [ 1634.059844]  [] 
nmi+0x56/0xa5


  As suggested, this is causing hard lockups and/or pauses.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 29 04:12 seq
   crw-rw 1 root audio 116, 33 Jun 29 04:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  

[Kernel-packages] [Bug 1753371] sos report

[bugproxy]

Default Comment by Bridge

** Attachment added: "sos report"
   
https://bugs.launchpad.net/bugs/1753371/+attachment/5100764/+files/sosreport-ltciofvtr-spoon4.165124-20180226004040.tar.xz

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

Title:
  Ubuntu 18.04 - Kernel crash on nvme subsystem-reset /dev/nvme0 (Bolt /
  NVMe)

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

Bug description:
  == Comment: #1 - NAVEED A. UPPINANGADY SALIH  -
  2018-02-25 23:45:13 ==

  
  == Comment: #6 - Wen Xiong  - 2018-02-27 10:41:23 ==
  hi Naveed,

  nvme subsystem-reset calls EEH recovery path. Is EEH recovery working
  with Bolt on this machine?

  Thanks,
  Wendy

  == Comment: #11 - Wen Xiong  - 2018-03-02 16:03:46 ==
  The following patch should fix the issue.

  http://lists.infradead.org/pipermail/linux-
  nvme/2018-February/015745.html

  It should be accepted into community soon. Keith has agreed to queue
  up for 4.16.

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

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

[Kernel-packages] [Bug 1761051] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  laptop sound broken in latest update -- "No output or input devices
  found"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after i installed the latest update for Kubuntu 17.10 my audio devices
  disappeared and i lost the ability to listen to music or play sounds
  on my laptop.  it worked fine before the update!

  (Caveat: sometimes ads or youtube will play through the speakers or
  headphones but it is unpredictable and i have no control over volume
  or muting.)

  the Plasma Audio Volume settings show "No Output Devices Available"
  and "No Input Devices Available".  it worked fine before the last
  update.

  this is a Lenovo P51, a fairly popular laptop for linux. my laptop is
  a high end version with an E3-1505M CPU and "hybrid graphics".

  i do not update the software every day so the problem may have been
  introduced upto two weeks ago, but no earlier then that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 21:38:36 2018
  HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20HHCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET31W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"

[craigster0]

i'm wondering whether i should try rolling back to the previous kernel
version.  (i didn't notice any updates to sound drivers or software when
i reviewed the packages to be upgraded, but i may have missed
something.)

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

Title:
  laptop sound broken in latest update -- "No output or input devices
  found"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after i installed the latest update for Kubuntu 17.10 my audio devices
  disappeared and i lost the ability to listen to music or play sounds
  on my laptop.  it worked fine before the update!

  (Caveat: sometimes ads or youtube will play through the speakers or
  headphones but it is unpredictable and i have no control over volume
  or muting.)

  the Plasma Audio Volume settings show "No Output Devices Available"
  and "No Input Devices Available".  it worked fine before the last
  update.

  this is a Lenovo P51, a fairly popular laptop for linux. my laptop is
  a high end version with an E3-1505M CPU and "hybrid graphics".

  i do not update the software every day so the problem may have been
  introduced upto two weeks ago, but no earlier then that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 21:38:36 2018
  HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20HHCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET31W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1761051] [NEW] laptop sound broken in latest update -- "No output or input devices found"

[craigster0]

Public bug reported:

after i installed the latest update for Kubuntu 17.10 my audio devices
disappeared and i lost the ability to listen to music or play sounds on
my laptop.  it worked fine before the update!

(Caveat: sometimes ads or youtube will play through the speakers or
headphones but it is unpredictable and i have no control over volume or
muting.)

the Plasma Audio Volume settings show "No Output Devices Available" and
"No Input Devices Available".  it worked fine before the last update.

this is a Lenovo P51, a fairly popular laptop for linux. my laptop is a
high end version with an E3-1505M CPU and "hybrid graphics".

i do not update the software every day so the problem may have been
introduced upto two weeks ago, but no earlier then that.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-37-generic 4.13.0-37.42
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: KDE
Date: Tue Apr  3 21:38:36 2018
HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02
InstallationDate: Installed on 2018-01-12 (81 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
MachineType: LENOVO 20HHCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-37-generic N/A
 linux-backports-modules-4.13.0-37-generic  N/A
 linux-firmware 1.169.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1UET31W (1.05 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P51
dmi.product.name: 20HHCTO1WW
dmi.product.version: ThinkPad P51
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful regression-update

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

Title:
  laptop sound broken in latest update -- "No output or input devices
  found"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after i installed the latest update for Kubuntu 17.10 my audio devices
  disappeared and i lost the ability to listen to music or play sounds
  on my laptop.  it worked fine before the update!

  (Caveat: sometimes ads or youtube will play through the speakers or
  headphones but it is unpredictable and i have no control over volume
  or muting.)

  the Plasma Audio Volume settings show "No Output Devices Available"
  and "No Input Devices Available".  it worked fine before the last
  update.

  this is a Lenovo P51, a fairly popular laptop for linux. my laptop is
  a high end version with an E3-1505M CPU and "hybrid graphics".

  i do not update the software every day so the problem may have been
  introduced upto two weeks ago, but no earlier then that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 21:38:36 2018
  HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20HHCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 

[Kernel-packages] [Bug 1760327] Re: linux: 4.4.0-119.143 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 4.4.0-119.143 -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:
  In Progress
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-release series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-119.143 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
  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/1760327/+subscriptions

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

[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13

[james guo]

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1758797

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

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

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

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

** Tags added: bionic

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

Title:
  [Ubuntu 18.04] USB Type-C test failed on GLK

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

Bug description:
  Description:

  Platform information:
  Label: GLK02SDP
  Processor: Silver N5000
  Bios: GELKRVPA.X64.0083.B30.1801162142
  OS: Ubuntu 18.04
  Kernel: 4.15.0-10-generic

  Details:
  Bios: system setup -> system component -> USB Type-C 

  root@GLK02:~# cat /boot/config-4.15.0-10-generic | grep -i ucsi
  CONFIG_TYPEC_UCSI=m
  CONFIG_UCSI_ACPI=m

  root@GLK02:~# ls /sys/class/typec/
  root@GLK02:~#

  USB Type-C ports could not be seen.

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

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

[Kernel-packages] [Bug 1761046] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed to build

[John Rutherford]

no idea what to report, hope the attahed info is beneficial

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  no idea what to report, hope the attached information is beneficial

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Wed Apr  4 10:51:01 2018
  InstallationDate: Installed on 2017-04-16 (352 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu4
  Python3Details: /usr/local/bin/python3.6, Python 3.6.2, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
  UpgradeStatus: Upgraded to bionic on 2018-03-30 (4 days ago)

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[Tyler Hicks]

Test kernels with the fix are available here:

http://people.canonical.com/~tyhicks/lp1759920/

You most likely only need linux-
image-4.13.0-38-generic_4.13.0-38.43+lp1759920.1_amd64.deb and linux-
image-extra-4.13.0-38-generic_4.13.0-38.43+lp1759920.1_amd64.deb

You should test that kernel without the noibpb and without the
apparmor=0 kernel command line options, and with the latest intel-
microcode package. When replying with testing feedback, please include
output from the following commands:

$ cat /proc/version_signature 
Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16
$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=c80800af-5af4-4235-9181-c366ef91c246 ro quiet splash vt.handoff=1
$ dmesg -t | grep -i microcode
microcode: microcode updated early to revision 0xc2, date = 2017-11-16
microcode: sig=0x406e3, pf=0x80, revision=0xc2
microcode: Microcode Update Driver: v2.2.

Thanks again for all of your help. This has been a tough one to track
down and it wouldn't have been possible without your 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/1759920

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1761046] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module failed to build

[John Rutherford]

Public bug reported:

no idea what to report, hope the attached information is beneficial

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
DKMSKernelVersion: 4.15.0-14-generic
Date: Wed Apr  4 10:51:01 2018
InstallationDate: Installed on 2017-04-16 (352 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageVersion: 6.30.223.271+bdcom-0ubuntu4
Python3Details: /usr/local/bin/python3.6, Python 3.6.2, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
UpgradeStatus: Upgraded to bionic on 2018-03-30 (4 days ago)

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


** Tags: amd64 apport-package bionic third-party-packages

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  no idea what to report, hope the attached information is beneficial

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Wed Apr  4 10:51:01 2018
  InstallationDate: Installed on 2017-04-16 (352 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu4
  Python3Details: /usr/local/bin/python3.6, Python 3.6.2, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4: bcmwl kernel module 
failed to build
  UpgradeStatus: Upgraded to bionic on 2018-03-30 (4 days ago)

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

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

[Kernel-packages] [Bug 1751990] PulseList.txt

[james guo]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100713/+files/PulseList.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] ProcModules.txt

[james guo]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100712/+files/ProcModules.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] UdevDb.txt

[james guo]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1751990/+attachment/5100715/+files/UdevDb.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] CRDA.txt

[james guo]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1751990/+attachment/5100704/+files/CRDA.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

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

[james guo]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100710/+files/ProcEnviron.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] ProcCpuinfo.txt

[james guo]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100709/+files/ProcCpuinfo.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

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

[james guo]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1751990/+attachment/5100708/+files/Lspci.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] RfKill.txt

[james guo]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1751990/+attachment/5100714/+files/RfKill.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] ProcInterrupts.txt

[james guo]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100711/+files/ProcInterrupts.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] WifiSyslog.txt

[james guo]

apport information

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

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] IwConfig.txt

[james guo]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100706/+files/IwConfig.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] JournalErrors.txt

[james guo]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100707/+files/JournalErrors.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] CurrentDmesg.txt

[james guo]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100705/+files/CurrentDmesg.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weilo  1661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
  InstallationDate: Installed on 2018-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shinelon Computer W65KJ1_KK1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65KJ1_KK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: W65KJ1_KK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Shinelon Computer

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

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

[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13

[james guo]

apport information

** Tags added: apport-collected

** Description changed:

  I have a laptop call dc pro. it is made in china. processor is Intel(R)
  Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The problems are:
  
  1 the ubuntu 16.04.03 installation will hang somewhere. luckily 16.04.02
  will go through.
  
  2 the system will not boot after upgrade to kernel 4.13. the old kernel
  4.8 will boot without problem.
  
  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" ) for
  the kernel 4.13, the old kernel 4.8 is ok though
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  weilo  1661 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697
+ InstallationDate: Installed on 2018-04-04 (0 days ago)
+ InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
+  Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Shinelon Computer W65KJ1_KK1
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
+ RelatedPackageVersions:
+  linux-restricted-modules-4.8.0-36-generic N/A
+  linux-backports-modules-4.8.0-36-generic  N/A
+  linux-firmware1.157.8
+ Tags:  xenial
+ Uname: Linux 4.8.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/10/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.05.05
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: W65KJ1_KK1
+ dmi.board.vendor: Notebook
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
+ dmi.product.name: W65KJ1_KK1
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: Shinelon Computer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1751990/+attachment/5100703/+files/AlsaInfo.txt

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: 

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[John Bryant]

It was working fine for a few minutes. I opened Firefox, played some
Hulu, opened Android Studio, connected my tablet, and all was well. When
I tried to allow USB debugging on the tablet, the system locked up.

I had been using 4.13.0-37 prior to trying the new microcode again, so
I'll revert the microcode and try the same sequence of events with the
newer 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/1759920

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1758797] Re: [Ubuntu 18.04] USB Type-C test failed on GLK

[Anthony Wong]

** Information type changed from Proprietary to Public

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

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

Title:
  [Ubuntu 18.04] USB Type-C test failed on GLK

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  Platform information:
  Label: GLK02SDP
  Processor: Silver N5000
  Bios: GELKRVPA.X64.0083.B30.1801162142
  OS: Ubuntu 18.04
  Kernel: 4.15.0-10-generic

  Details:
  Bios: system setup -> system component -> USB Type-C 

  root@GLK02:~# cat /boot/config-4.15.0-10-generic | grep -i ucsi
  CONFIG_TYPEC_UCSI=m
  CONFIG_UCSI_ACPI=m

  root@GLK02:~# ls /sys/class/typec/
  root@GLK02:~#

  USB Type-C ports could not be seen.

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

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

[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Alistair Buxton]

Some more: touching the system cache files doesn't make it work.

Binary diff on the cache files before and after running fc-cache shows
this:

63 c7 c3 5a 00 00 00 00  47 72 ce 15 00 00 00 00
63 c7 c3 5a 00 00 00 00  00 00 00 00 00 00 00 00

Before, at offset 0x38, the "bad" cache files have a non-zero 32 bit
number. The number is different in every "bad" cache file. It is always
zero in the "good" files. This is the only difference. The rest of each
file is identical.

I don't know what this field represents. Need a fontconfig expert to
look at this.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[John Bryant]

It works so far with apparmor=0, and jams without it. I'll keep running
it for a while to see if it stays stable.

I used a slightly different method of getting the latest microcode:
sudo apt-mark unhold intel-microcode
sudo apt upgrade

This ran update-initramfs on 4.13.0-38, so everything should be up to
date.

Also, I don't have sssd 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/1759920

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1760973] Re: virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel

[dino99]

Same Bug #1760876

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

Title:
  virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build
  [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel"]

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

Bug description:
  crash while upgrading today

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.8-dfsg-5
  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-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 16:27:06 2018
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  PackageArchitecture: all
  PackageVersion: 5.2.8-dfsg-5
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.2.8-dfsg-5: virtualbox 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/linux/+bug/1760973/+subscriptions

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

[Kernel-packages] [Bug 1760876] Re: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build

[dino99]

Also reported at lp:#1760973

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

Title:
  fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel
  module failed to build

Status in fwts package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Was installing the kernel 4.15.0-14-generic when that crash happened.
  Now libelf-dev is requested and need to be added as a dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 15:39:06 2018
  PackageVersion: 18.03.00-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fwts
  Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms 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/fwts/+bug/1760876/+subscriptions

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

[Kernel-packages] [Bug 1761035] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  dont know what exactly the error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dont know what exactly the error

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ram1747 F pulseaudio
  Date: Sun Apr  1 12:12:22 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: dentry_unlink_inode+0x11a/0x140 RSP: ae6e8189fb60
  Failure: oops
  HibernationDevice: RESUME=UUID=bba6e818-1344-4359-9b12-66eec53e4051
  InstallationDate: Installed on 2018-03-21 (13 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  MachineType: Acer Aspire 5750
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-14-generic 
root=UUID=b221dbc3-b4d6-4699-b244-0e9d7063521d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0208
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.16
  dmi.modalias: 
dmi:bvnAcer:bvrV1.16:bd10/24/2011:svnAcer:pnAspire5750:pvrV1.16:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.16:
  dmi.product.name: Aspire 5750
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1760973] Re: virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel

[Daniel van Vugt]

** Summary changed:

- virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build
+ virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build 
[Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"]

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

Title:
  virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build
  [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel"]

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

Bug description:
  crash while upgrading today

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.8-dfsg-5
  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-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 16:27:06 2018
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  PackageArchitecture: all
  PackageVersion: 5.2.8-dfsg-5
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.2.8-dfsg-5: virtualbox 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/linux/+bug/1760973/+subscriptions

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

[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Alistair Buxton]

Another piece of the puzzle: if you run:

sudo fc-cache -fv

this will rebuild the system font cache in /var/cache/fontconfig

If you then delete the user's cache in ~/.cache/fontconfig and re-log,
there is no delay... and the user's font cache will NOT be rebuilt.

After a delayed login, user's cache and the system cache appear to
contain the same files.

So it looks as if something thinks the system cache is out of date and
wants to rebuild it. Whatever it is only has user permissions, so
rebuilds the font cache in the user's .cache

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Kernel-packages] [Bug 1761035] Re: dont know what exactly the error

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  dont know what exactly the error

Status in linux package in Ubuntu:
  New

Bug description:
  dont know what exactly the error

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ram1747 F pulseaudio
  Date: Sun Apr  1 12:12:22 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: dentry_unlink_inode+0x11a/0x140 RSP: ae6e8189fb60
  Failure: oops
  HibernationDevice: RESUME=UUID=bba6e818-1344-4359-9b12-66eec53e4051
  InstallationDate: Installed on 2018-03-21 (13 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  MachineType: Acer Aspire 5750
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-14-generic 
root=UUID=b221dbc3-b4d6-4699-b244-0e9d7063521d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0208
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.16
  dmi.modalias: 
dmi:bvnAcer:bvrV1.16:bd10/24/2011:svnAcer:pnAspire5750:pvrV1.16:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.16:
  dmi.product.name: Aspire 5750
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1245328] Re: Synaptics kernel driver does not report finger width information, breaking usermode driver's palm detection

[NJ]

@Durieux

I am unsure this is the place for such questions, but the answers are as
follows (at least for Linux Mint).

Run the package manager that is called (confusingly) Synaptics. You
should be able to find it in a menu under that name or under a name such
as 'package manager'. Search for and install the package 'xserver-xorg-
input-libinput'. Search for and uninstall the package 'xserver-xorg-
input-synaptics'. Were you to have both installed at once, one - I do
not know which - would likely take precedence over the other. The worst
that could happen with any of this is that you end up with no
functioning driver and have to use the keyboard and/or terminal to
ensure that you have one of the drivers 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/1245328

Title:
  Synaptics kernel driver does not report finger width information,
  breaking usermode driver's palm detection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While doing some work on the Xorg synaptics driver, I noticed that we
  never actually detect palm blocking even after running synclient
  PalmDetect=1. Digging in a bit, the driver claims in its capability
  bits that it should be sending ABS_TOOL_WIDTH records, but according
  to evtest(1), the driver never sends these advertised records to
  userspace. As a result, the Xorg synaptics driver never sees
  hw->fingerWidth become non-zero in SynapticsDetectFinger and never
  detects that I've mashed my palm into the large touchpad on this
  machine.

  Expected:

  Kill X. Run evtest(1). Select touchpad device. Move touchpad. See
  ABS_TOOL_WIDTH records in the event stream.

  Actual:

  No ABS_TOOL_WIDTH records even though the device claims to support
  them in its capability bits.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: 
boot/vmlinuz-3.11.0-12-generic]
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dancol 2258 F pulseaudio
  Date: Sun Oct 27 21:43:01 2013
  HibernationDevice: RESUME=UUID=7da7377a-42c7-49f8-a060-8dee466c61fd
  InstallationDate: Installed on 2013-10-23 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 34601F5
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 2059198
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET96WW(2.56):bd04/29/2013:svnLENOVO:pn34601F5:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 34601F5
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic

[Daniel van Vugt]

** Tags added: xenial

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

Title:
  bluetoothd[650]: Failed to obtain handles for "Service Changed"
  characteristic

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain 
handles for "Service Changed" characteristic
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link 
Loss service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service 
could not be registered
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: 
Input/output error (5)
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver 
initialization failed.
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation 
not permitted (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.34-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 25 16:37:42 2015
  InstallationDate: Installed on 2015-07-26 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  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.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0
TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0

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

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

[Kernel-packages] [Bug 1760327] Re: linux: 4.4.0-119.143 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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/1760327

Title:
  linux: 4.4.0-119.143 -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:
  In Progress
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-release series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-119.143 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
  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/1760327/+subscriptions

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

[Kernel-packages] [Bug 1761035] [NEW] dont know what exactly the error

[Sanjeev raghuwanshi]

Public bug reported:

dont know what exactly the error

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
Uname: Linux 4.15.0-13-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ram1747 F pulseaudio
Date: Sun Apr  1 12:12:22 2018
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: dentry_unlink_inode+0x11a/0x140 RSP: ae6e8189fb60
Failure: oops
HibernationDevice: RESUME=UUID=bba6e818-1344-4359-9b12-66eec53e4051
InstallationDate: Installed on 2018-03-21 (13 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
MachineType: Acer Aspire 5750
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-14-generic 
root=UUID=b221dbc3-b4d6-4699-b244-0e9d7063521d ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: unable to handle kernel NULL pointer dereference at 0208
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE50_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.16
dmi.modalias: 
dmi:bvnAcer:bvrV1.16:bd10/24/2011:svnAcer:pnAspire5750:pvrV1.16:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.16:
dmi.product.name: Aspire 5750
dmi.product.version: V1.16
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-kerneloops bionic kernel-oops

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

Title:
  dont know what exactly the error

Status in linux package in Ubuntu:
  New

Bug description:
  dont know what exactly the error

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ram1747 F pulseaudio
  Date: Sun Apr  1 12:12:22 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: dentry_unlink_inode+0x11a/0x140 RSP: ae6e8189fb60
  Failure: oops
  HibernationDevice: RESUME=UUID=bba6e818-1344-4359-9b12-66eec53e4051
  InstallationDate: Installed on 2018-03-21 (13 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  MachineType: Acer Aspire 5750
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-14-generic 
root=UUID=b221dbc3-b4d6-4699-b244-0e9d7063521d ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0208
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.16
  dmi.modalias: 
dmi:bvnAcer:bvrV1.16:bd10/24/2011:svnAcer:pnAspire5750:pvrV1.16:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.16:
  dmi.product.name: Aspire 5750
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1760327] Re: linux: 4.4.0-119.143 -proposed tracker

[Chris Wayne]

No regressions found during automated snap testing, +1 to move to
candidate channel (Details here: https://trello.com/c/0XMRZL8M/226-pc-
kernel-440-119143-109)

** Changed in: kernel-sru-workflow/snap-certification-testing
   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/1760327

Title:
  linux: 4.4.0-119.143 -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:
  In Progress
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-release series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-119.143 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
  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/1760327/+subscriptions

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

[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Alistair Buxton]

seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Alistair Buxton]

As far as the original bug with delayed login goes... it seems that the
Bluetooth stuff is a red herring.

Since it only happens on first login, I deleted the contents of ~ and
relogged. The delay came back, so I bisected the files until I arrived
at the single file which needs to be deleted in order for the delay to
happen. And that file is:

   ~/.cache/fontconfig/9b89f8e3dae116d678bbf48e5f21f69b-le32d4.cache-7

This cache file is associated with the Noto CJK fonts at:

/usr/share/fonts/opentype/noto

(You can see this by running strings on it.)

Deleting this file while the user is not logged in causes the next login
to take 60 seconds.

** Bug watch added: Debian Bug tracker #845058
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[Gordon Lack]

I've since left the 4.13.0-38-generic kernel + 3.20180312 microcode +
apparmor=0 option running for >30 mins (top constantly running plus a
short compilation using all 4 cores in parallel, make -j4, of a github
download).

It still looked OK.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1715519] Re: bnx2x_attn_int_deasserted3:4323 MC assert!

[Daniel Axtens]

Hi,

We do ship an iso for ppc64le for Trusty - I'm not sure whether it does
bare metal/PowerNV or just as an LPAR under PowerVM, but it's probably a
bit moot at this point.

The good news is that as you can see, the artful kernel was released with the 
fix.
The Xenial kernel also contains the fix; I'm not sure why that wasn't 
auto-added to this bug, but the release notes contain this fix: 
https://launchpad.net/ubuntu/+source/linux/4.4.0-119.143

I am not sure what the final status of the patch in Trusty is, I will
let you know when I find out.

Regards,
Daniel

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

Title:
  bnx2x_attn_int_deasserted3:4323 MC assert!

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  SRU Justification
  =

  A ppc64le system runs as a guest under PowerVM. This guest has a bnx2x
  card attached, and uses openvswitch to bridge an ibmveth interface for
  traffic from other LPARs.

  We see the following crash sometimes when running netperf:
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4323(enP24p1s0f2)]MC assert!
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:720(enP24p1s0f2)]XSTORM_ASSERT_LIST_INDEX 0x2
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:736(enP24p1s0f2)]XSTORM_ASSERT_INDEX 0x0 = 0x 
0x25e42a7e 0x00462a38 0x00010052
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_mc_assert:750(enP24p1s0f2)]Chip Revision: everest3, FW Version: 7_13_1
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_attn_int_deasserted3:4329(enP24p1s0f2)]driver assert
  May 10 17:16:32 tuk6r1phn2 kernel: bnx2x: 
[bnx2x_panic_dump:923(enP24p1s0f2)]begin crash dump -
  ... (dump of registers follows) ...

  Subsequent debugging reveals that the packets causing the issue come
  through the ibmveth interface - from the AIX LPAR. The veth protocol
  is 'special' - communication between LPARs on the same chassis can use
  very large (64k) frames to reduce overhead. Normal networks cannot
  handle such large packets, so traditionally, the VIOS partition would
  signal to the AIX partitions that it was 'special', and AIX would send
  regular, ethernet-sized packets to VIOS, which VIOS would then send
  out.

  This signalling between VIOS and AIX is done in a way that is not
  standards-compliant, and so was never made part of Linux. Instead, the
  Linux driver has always understood large frames and passed them up the
  network stack.

  In some cases (e.g. with TCP), multiple TCP segments are coalesced
  into one large packet. In Linux, this goes through the generic receive
  offload code, using a similar mechanism to GSO. These segments can be
  very large which presents as a very large MSS (maximum segment size)
  or gso_size.

  Normally, the large packet is simply passed to whatever network
  application on Linux is going to consume it, and everything is OK.

  However, in this case, the packets go through Open vSwitch, and are
  then passed to the bnx2x driver. The bnx2x driver/hardware supports
  TSO and GSO, but with a restriction: the maximum segment size is
  limited to around 9700 bytes. Normally this is more than adequate.
  However, if a large packet with very large (>9700 byte) TCP segments
  arrives through ibmveth, and is passed to bnx2x, the hardware will
  panic.

  [Impact]

  bnx2x card panics, requiring power cycle to restore functionality.

  The workaround is turning off TSO, which prevents the crash as the
  kernel resegments *all* packets in software, not just ones that are
  too big. This has a performance cost.

  [Fix]

  Test packet size in bnx2x feature check path and disable GSO if it is
  too large. To do this we move a function from one file to another and
  add another in the networking core.

  [Regression Potential]

  A/B/X: The changes to the network core are easily reviewed. The changes to 
behaviour are limited to the bnx2x card driver.
  The most likely failure case is a false-positive on the size check, which 
would lead to a performance regression only.

  T: This also involves a different change to the networking core to add
  the old-style GSO checking, which is more invasive. However the
  changes are simple and easily reviewed.

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[Gordon Lack]

> if someone affected wanted to boot with the apparmor=0 kernel command
line option (with the latest artful kernel, without the noibpb kernel
command line option, and with the latest intel-microcode package), I'd
really appreciate it.

Just done this:

Downloaded latest microcode (3.20180312).
Replaced /lib/firmware/intel-ucode with one from the download.
Ran update-initramfs -u -k 4.13.0-38-generic
Rebooted - specifically selected 4.13.0-38-generic to reboot.
Added apparmor=0 as a boot option.
Booted.

=> All looks OK. System still up and running after 5 mins.

Rebooted to 4.13.0-38-generic without specifying apparmor=0.

=> System locks up at the "pulsing" kubuntu logo.

Rebooted back to 4.13.0-38-generic with apparmor=0 (and
fsck.mode=force) to switch back to the previous microcode on
4.13.0-38-generic.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[Mike Pontillo]

@tyhicks, I don't have an Artful test system, but I confirmed on Xenial
(4.4.0-116-generic) that `apparmor=0` is a workaround, without the
`noibpb` option and with intel-microcode version
3.20180312.0~ubuntu16.04.1.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[Tyler Hicks]

I think that I've figured out this lockup thanks to some information in
duplicate bugs. Specifically, this comment:

https://bugs.launchpad.net/ubuntu/+source/intel-
microcode/+bug/1760264/comments/7

as well as the nice git bisect work of jsalisbury that I recently
discovered in bug 1746418. This is the problematic commit:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/artful/commit/?id=96d520d

When the kernel does a task switch due to a task that was confined by
AppArmor exiting, the task's pi_lock is taken in the exit() path and
then switch_mm() is calling ___ptrace_may_access() which then calls down
into apparmor which then calls into audit if the old task can't ptrace
the new task. Eventually, the audit subsystem tries to take the pi_lock
again when waking up the task.

This would be a little easier to be sure of with a nice lockdep warning
from a debug kernel build but I'm fairly sure this is what's going on. I
suspect that swapping out the commit above with this upstream commit
will fix the problem:

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

It doesn't call into AppArmor to see if IBPB should be used when
switching tasks. I'll build a test kernel for affected folks to test
with. In the meantime, if someone affected wanted to boot with the
apparmor=0 kernel command line option (with the latest artful kernel,
without the noibpb kernel command line option, and with the latest
intel-microcode package), I'd really appreciate it.

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic

[gaetano1984]

the solution below to my conf doesn't work. keep needing help :**(


I temporary fixed it doing this: stop bluetooth, kill bluetoothd and obexd, 
start bluetooth:

$ sudo systemctl stop bluetooth
$ sudo killall -TERM bluetoothd
$ sudo killall -TERM obexd
$ sudo systemctl start bluetooth

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

Title:
  bluetoothd[650]: Failed to obtain handles for "Service Changed"
  characteristic

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain 
handles for "Service Changed" characteristic
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link 
Loss service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service 
could not be registered
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: 
Input/output error (5)
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver 
initialization failed.
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation 
not permitted (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.34-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 25 16:37:42 2015
  InstallationDate: Installed on 2015-07-26 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  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.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0
TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0

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

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

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

[Pascal Mons]

Furthermore I would like to know what driver I should use and which to
keep blacklisted. On this webpage:

https://wiki.archlinux.org/index.php/broadcom_wireless

I see the following:

Device inaccessible after kernel upgrade

Since the 3.3.1 kernel the bcma module was introduced. If using a brcm80211 
driver be sure it has not been blacklisted. It should be blackisted if using a 
b43 driver.

If you are using broadcom-wlAUR, uninstall and reinstall it after
upgrading your kernel or switch to broadcom-wl-dkms package.

>From the Broadcom doc. available at:


I have this entry

14e4:4331   firmware-b43-installer
firmware-b43-installer<---  Broadcom Limited BCM4331 802.11a/b/g/n

meaning the driver to use is in package 'firmware-b43-installer' (a b43
driver)

So, from what I see I shouldn't use bcma ...

in /etc/modprobe.d/blaclist-bcm43.conf I have

# Warning: This file is autogenerated by bcmwl. All changes to this file will 
be lost.
blacklist b43
blacklist b43legacy
blacklist ssb
blacklist bcm43xx
blacklist brcm80211
blacklist brcmfmac
blacklist brcmsmac
blacklist bcma

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
     ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
     ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt- ABWMgmt-
   Capabilities: [100 v1] Advanced Error Reporting
    UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
    UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
    CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
   Capabilities: [13c v1] Virtual Channel
    Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
    Arb:Fixed- WRR32- WRR64- WRR128-
    Ctrl:   ArbSelect=Fixed
    Status: InProgress-
    VC0:Caps:   

[Kernel-packages] [Bug 1760973] Re: virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

[Bug Watch Updater]

** Changed in: linux (Debian)
   Status: Unknown => 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/1760973

Title:
  virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

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

Bug description:
  crash while upgrading today

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.8-dfsg-5
  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-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 16:27:06 2018
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  PackageArchitecture: all
  PackageVersion: 5.2.8-dfsg-5
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.2.8-dfsg-5: virtualbox 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/linux/+bug/1760973/+subscriptions

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

[Kernel-packages] [Bug 1760108] Re: Broadcom B43 Wireless Driver Not Functional after Update to Linux Kernel 4.15

[Pascal Mons]

That's not really the case. For more information on the situation of
Broadcom drivers on my system I will refer you to my Ask Ubuntu
question:

https://askubuntu.com/questions/1012880/suddenly-the-wi-fi-broadcom-5
-ghz-interface-is-shown-out-of-range-permanently/1021178#1021178

You are true that when installing either kernel 4.15 or 4.16 I get this
dkms error:

Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.15.0-13-generic 
/boot/vmlinuz-4.15.0-13-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.15.0-13-generic 
/boot/vmlinuz-4.15.0-13-generic
ERROR (dkms apport): kernel package linux-headers-4.15.0-13-generic is not 
supported
Error! Bad return status for module build on kernel: 4.15.0-13-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
information.
[...]
Setting up linux-image-extra-4.15.0-13-generic (4.15.0-13.14~16.04.1) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.15.0-13-generic 
/boot/vmlinuz-4.15.0-13-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.15.0-13-generic 
/boot/vmlinuz-4.15.0-13-generic
ERROR (dkms apport): kernel package linux-headers-4.15.0-13-generic is not 
supported
Error! Bad return status for module build on kernel: 4.15.0-13-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
information.
[...]

And when installing kernek 4.13 I get no error.

I had similar dkms error as well for the nVidia Graphics Drivers not up
to date i.e. not build with the appropriate patches for the target
kernel.

So I guess there might be some problem lingering with the bcmwl-kernel-
source driver.

Right now I am in kernel 4.13 and typing:

$ cat /etc/modprobe.d/* | egrep 'bcm'
# Warning: This file is autogenerated by bcmwl. All changes to this file will 
be lost.
blacklist bcm43xx
blacklist bcma
$ 

So bcma and bcm43xx are currently blacklisted.

And I have my wi-fi connection dropped at random ... several times an
hour.

Still your answer does not explain why the network adapter is
'UNCLAIMED' in 4.15 ? while it is seen in 4.16 ?

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

Title:
  Broadcom B43 Wireless Driver Not Functional after Update to Linux
  Kernel 4.15

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

Bug description:
  I was upgrading my Ubuntu Xenial 16.04 from linux-hwe kernel 4.13.0-38
  to linux-hwe-edge 4.15.0-13.

  After reboot my Broadcom network adapter (requiring package
  firmware-b43-installer) is not recognized by the new kernel 4.15.0-13.

  Running the lspci command lists the device as 'UNCLAIMED' in linux
  kernel 4.15.

  $ lspci
  [...]
  *-pci:4
   description: PCI bridge
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 1c
   bus info: pci@:00:1c.0
   version: f0
   width: 32 bits
   clock: 33MHz
   capabilities: pci pciexpress msi pm normal_decode bus_master 
cap_list
   configuration: driver=pcieport
   resources: irq:123 memory:ef50-ef5f
     *-network UNCLAIMED
  description: Network controller
  product: BCM4331 802.11a/b/g/n
  vendor: Broadcom Corporation
  physical id: 0
  bus info: pci@:05:00.0
  version: 02
  width: 64 bits
  clock: 33MHz
  capabilities: pm msi pciexpress cap_list
  configuration: latency=0
  resources: memory:ef50-ef503fff
  [...]
  $

  The lspci -vv -pci:4 commands with the relevant devices are shown
  below.

  $ lspci -vv -pci:4
  [...]
  05:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 
02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
    Address:   Data: 
   Capabilities: [d0] Express (v1) Endpoint, MSI 00
    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
     ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
     RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
     MaxPayload 128 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<4us, L1 <64us
    

[Kernel-packages] [Bug 1760110] Re: Kernel 4.15.0-13.14 reboots instead of powering off (when on battery) on HP Spectre x360 ae-000x

[Dmitry Malykhanov]

Generally 4.16.0-041600.201804012230 seems to have the same problem.
"Generally" means that 4.16 behaviour seems to be even more random -
sometimes it powers off correctly, and sometimes it does not power off
even on AC (and reboots). Unfortunately, I could not figure out the
exact rules and conditions. However, most of the time 4.16 fails to cut
the power and reboots the box instead.

And 4.15.0-10.11 is rock solid, always powers off as expected.

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

Title:
  Kernel 4.15.0-13.14 reboots instead of powering off (when on battery)
  on HP Spectre x360 ae-000x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This might be a duplicate of #1756455

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-13 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot instead of turning hardware off. 4.15.0-12 has the same problem
  (see #1756455). Booting with kernel 4.15.0-10 resolves the issue,
  system turns off power and stays powered off.

  * secure boot enabled or disabled makes no difference

  * kernel 4.15.0-10 correctly powers off system (halt -p) every time,
  power source makes no difference

  * kernel 4.15.0-13 correctly powers off system only when running on AC

  * kernel 4.15.0-13 does NOT power off system (reboots instead) when AC
  power is NOT connected (running on battery) every time

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1648 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar 30 14:39:28 2018
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1760110] Re: Kernel 4.15.0-13.14 reboots instead of powering off (when on battery) on HP Spectre x360 ae-000x

[Dmitry Malykhanov]

** Tags added: kernel-bug-exists-upstream

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

Title:
  Kernel 4.15.0-13.14 reboots instead of powering off (when on battery)
  on HP Spectre x360 ae-000x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This might be a duplicate of #1756455

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-13 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot instead of turning hardware off. 4.15.0-12 has the same problem
  (see #1756455). Booting with kernel 4.15.0-10 resolves the issue,
  system turns off power and stays powered off.

  * secure boot enabled or disabled makes no difference

  * kernel 4.15.0-10 correctly powers off system (halt -p) every time,
  power source makes no difference

  * kernel 4.15.0-13 correctly powers off system only when running on AC

  * kernel 4.15.0-13 does NOT power off system (reboots instead) when AC
  power is NOT connected (running on battery) every time

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1648 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar 30 14:39:28 2018
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1760327] Re: linux: 4.4.0-119.143 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   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/1760327

Title:
  linux: 4.4.0-119.143 -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:
  In Progress
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-release series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-119.143 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
  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/1760327/+subscriptions

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

[Kernel-packages] [Bug 1760973] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

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

Bug description:
  crash while upgrading today

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.8-dfsg-5
  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-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 16:27:06 2018
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  PackageArchitecture: all
  PackageVersion: 5.2.8-dfsg-5
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.2.8-dfsg-5: virtualbox 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/linux/+bug/1760973/+subscriptions

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

[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[TJ]

This is a command-line that is useful for manually exercising the
org.bluez DBus activiation. It might reproduce the timeout or otherwise
give useful clues. Command should be all on one line (ignore Launchpad
line wrapping):

dbus-send --system --print-reply --dest=org.bluez /
org.freedesktop.DBus.ObjectManager.GetManagedObjects

I won't reproduce the entire output here but this is the initial part
when a BT hci device is available:

method return time=1522790434.404190 sender=:1.2 -> destination=:1.399 
serial=821 reply_serial=2
   array [
  dict entry(
 object path "/org/bluez"
 array [
dict entry(
   string "org.freedesktop.DBus.Introspectable"
   array [
   ]
)
dict entry(
   string "org.bluez.AgentManager1"
   array [
   ]
)
dict entry(
   string "org.bluez.ProfileManager1"
   array [
   ]
)
 ]
  )
  dict entry(
 object path "/org/bluez/hci0"

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Kernel-packages] [Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial

[Jeff Lane]

It looks like this happened perhaps sometime between 4.10 and 4.13:

4.4.0-112: 
https://certification.canonical.com/hardware/201802-26096/submission/127640/
Driver: ixgbe (ver: 4.2.1-k)
Shows proper speed for both ports

4.10.0-42: 
https://certification.canonical.com/hardware/201712-26025/submission/125481/
Driver: ixgbe (ver: 4.4.0-k)
Shows proper speed for both ports

4.13.0-37: 
https://certification.canonical.com/hardware/201803-26156/submission/128508/
Driver: ixgbe (ver: 5.1.0-k)
Shows -1 for second port

4.16.0-041600rc6 (tester sent via email)
Driver version unknown
Shows -1 for second port

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

Title:
  Intel NICs not properly reporting link speed in SysFS in Xenial

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Triaged

Bug description:
  This was discovered during certification testing of 16.04.4 (I've now
  seen this behaviour at least 2 times)

  A system under test has a 2 port Intel X550 NIC (10Gb)

  Udev reports the NIC as this:
  Category: NETWORK
  Interface: enp94s0f0
  Product: Ethernet Controller 10G X550T
  Vendor: Intel Corporation
  Driver: ixgbe (ver: 5.1.0-k)
  Path: /devices/pci:5d/:5d:00.0/:5e:00.0
  ID:   [8086:1563]
  Subsystem ID: [152d:8a13]

  Ethtool shows this info (this is for the second port, which has the issue)
  Settings for enp94s0f1:
   Supported ports: [ TP ]
   Supported link modes:   100baseT/Full
   1000baseT/Full
   1baseT/Full
   Supported pause frame use: Symmetric
   Supports auto-negotiation: Yes
   Advertised link modes:  100baseT/Full
   1000baseT/Full
   1baseT/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Speed: 1Mb/s
   Duplex: Full
   Port: Twisted Pair
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   MDI-X: Unknown
   Supports Wake-on: umbg
   Wake-on: g
   Current message level: 0x0007 (7)
    drv probe link
   Link detected: yes

  Note ethtool shows an active 10Gb link.

  The test tool determines the NIC speed by introspecting the sysfs data
  for each NIC port.  In this case, by looking at
  /sys/class/net/DEVICENAME/speed

  I've now seen this on a couple different NICs using the ixgbe driver.
  The first port will properly show connected link speed in
  /sys/class/net/DEVICENAME/speed but the second port shows -1 in that
  file.

  Because of this, certification tests are failing because the tool
  believes that the link speed is incorrect.

  This current example is using kernel 4.13.0-37.42~16.04.1

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

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

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

[Lucas Zanella]

I'm trying since you wrote. No problems yet on the host machine, but the
virtual machine already presented the error twice today (not related to
high disk usage)

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

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

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

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

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

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

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

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

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

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

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

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

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

[Kernel-packages] [Bug 1760876] Re: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build

[Launchpad Bug Tracker]

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

** Changed in: fwts (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/1760876

Title:
  fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel
  module failed to build

Status in fwts package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Was installing the kernel 4.15.0-14-generic when that crash happened.
  Now libelf-dev is requested and need to be added as a dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 15:39:06 2018
  PackageVersion: 18.03.00-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fwts
  Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms 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/fwts/+bug/1760876/+subscriptions

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

[Kernel-packages] [Bug 1760973] Re: virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

[LocutusOfBorg]

please linux folks, add libelf-dev dependency or revert the config
fstack protector change, as Debian did, to fix dkms packages

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

Title:
  virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

Status in linux package in Ubuntu:
  New
Status in linux package in Debian:
  Unknown

Bug description:
  crash while upgrading today

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.8-dfsg-5
  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-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 16:27:06 2018
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  PackageArchitecture: all
  PackageVersion: 5.2.8-dfsg-5
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.2.8-dfsg-5: virtualbox 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/linux/+bug/1760973/+subscriptions

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

[Kernel-packages] [Bug 1760973] Re: virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

[LocutusOfBorg]

install libelf-dev package, this seems to be a linux issue

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

** Bug watch added: Debian Bug tracker #886474
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474

** Also affects: linux (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474
   Importance: Unknown
   Status: Unknown

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

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

Title:
  virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

Status in linux package in Ubuntu:
  New
Status in linux package in Debian:
  Unknown

Bug description:
  crash while upgrading today

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.8-dfsg-5
  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-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 16:27:06 2018
  InstallationDate: Installed on 2018-01-12 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  PackageArchitecture: all
  PackageVersion: 5.2.8-dfsg-5
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.2.8-dfsg-5: virtualbox 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/linux/+bug/1760973/+subscriptions

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

[Kernel-packages] [Bug 1760973] [NEW] virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

crash while upgrading today

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: virtualbox-dkms 5.2.8-dfsg-5
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-0ubuntu2
Architecture: amd64
DKMSKernelVersion: 4.15.0-14-generic
Date: Tue Apr  3 16:27:06 2018
InstallationDate: Installed on 2018-01-12 (81 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
PackageArchitecture: all
PackageVersion: 5.2.8-dfsg-5
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: virtualbox
Title: virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic third-party-packages
-- 
virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build
https://bugs.launchpad.net/bugs/1760973
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[TJ]

The Dbus bluze system config doesn't run, it has "Exec=/bin/false" --
/usr/share/dbus-1/system-services/org.bluez.service It's left to systemd
to activate it via /lib/systemd/system/bluetooth.service

[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
ProtectHome=true
ProtectSystem=full

[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service

I would suspect if there are no BT hci devices then bluetooth.service
won't run.

So the question is, are the other flavours doing something to allow a
'dummy' BT device so bluetooth service runs and org.bluez is available
or is it that their Bluetooth tooling isn't calling the DBus interface
at all (using libbluetooth directly maybe) ?

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

[QkiZ]

** Attachment added: "intel-microcode.crash"
   
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+attachment/5100323/+files/intel-microcode.crash

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

Title:
  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
  image-4.13.0-37-generic)

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in intel-microcode source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in intel-microcode source package in Artful:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to
  boot.

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
 https://wiki.ubuntu.com/Kernel/KernelBootParameters
  2. Install the previous version of package from
 
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb
  3. (Optional) Hold the package so that it won't be upgraded accidentally
 sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions

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

[Kernel-packages] [Bug 1760327] Re: linux: 4.4.0-119.143 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-119.143 -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:
  In Progress
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-release series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-119.143 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
  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/1760327/+subscriptions

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

[Kernel-packages] [Bug 1759791] Re: NFS + sec=krb5 is broken

[Joseph Salisbury]

This is actually a commit in linux-next that appears to be the fix to
this bug.  I built a test kernel with this patch, which is commit
190b22eedd032c14cbc2b9e13d112f039460522c.

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

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  NFS + sec=krb5 is broken

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

Bug description:
  I am testing the development branch of Bionic Beaver.
  With the latest update to kernel 4.15.0-13 my nfs-mounts in a university 
network are broken.

  > sudo mount -vvv -t nfs4 my_server:/my/share  /nfs -osoft,sec=krb5
  > mount.nfs4: timeout set for Mon Mar 26 16:29:56 2018
  > mount.nfs4: trying text-based options 
'soft,sec=krb5,nfsvers=4.0,addr=10.162.229.2,clientaddr=10.152.249.189'
  > mount.nfs4: mount(2): Input/output error
  > mount.nfs4: mount system call failed

  > kernel: NFS: nfs4_discover_server_trunking unhandled error -5. Exiting with 
error EIO
  > kernel: RPC: couldn't encode RPC header, exit EIO
  > kernel: gss_marshal: gss_get_mic FAILED (851968)

  
  Known good version: linux-image-4.15.0-10

  I think it is the same bug like in 
https://bugzilla.redhat.com/show_bug.cgi?id=1558977
  The bug was introduced in the mainline kernel 4.15.4 with commit 
"[46e8d06e423c4f35eac7a8b677b713b3ec9b0684] crypto: hash - prevent using keyed 
hashes without setting key"

  This bug should be fixed before releasing ubuntu18.04 by either reverting the 
commit or using a fixed mainline kernel.
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1340 F pulseaudio
   /dev/snd/controlC0:  gdm1340 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-22 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046a:b091 Cherry GmbH 
   Bus 001 Device 002: ID 0bf8:101e Fujitsu Siemens Computers 
   Bus 001 Device 004: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO D757
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=463c4c1b-7771-40dd-833f-f4d68a5fd914 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UnreportableReason: Der Bericht gehört zu einem nicht installierten Paket.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 10/12/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.14.0 for D3531-A1x
  dmi.board.name: D3531-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3531-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.14.0forD3531-A1x:bd10/12/2017:svnFUJITSU:pnESPRIMOD757:pvr:rvnFUJITSU:rnD3531-A1:rvrS26361-D3531-A1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: ESPRIMO-FTS
  dmi.product.name: ESPRIMO D757
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

[Seth Forshee]

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

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

Title:
  Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default
  machine type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Seth Forshee]

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
    Installed: 4.13.0-16.19
    Candidate: 4.13.0-16.19
    Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  It appears that since the initramfs loads the bcache module which
  probes and finds all of the cache devices and backing devices then
  once the rootfs is mounted and udev gets to run, the bcache kernel
  module does not emit the CACHED_UUID value into the environment if the
  underlying devices are already registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
    register_bdev()
  bch_cached_dev_run()
    kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes:
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  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:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   

[Kernel-packages] [Bug 1758910] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From gwal...@br.ibm.com 2018-04-03 15:24 EDT---
Hi Seth,

Thank you, I see all of those patches already on the master-next branch.

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

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

[Seth Forshee]

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

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

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

Title:
  FFe: Enable configuring resume offset via sysfs

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1759445] Re: kernel panic when trying to reboot in bionic

[Jason Hobbs]

After updating firmware on the servers, we can't reproduce it at all
anymore.

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

Title:
  kernel panic when trying to reboot in bionic

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

Bug description:
  cpe_foundation test deployment of Bionic failed.
  After some investigation, it looks like the nodes deployed and installed 
bionic, but never came back from a reboot.

  Accessing the ILO console of a node in question (all nodes failed), it
  revealed a kernel panic (attached)

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

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

[Kernel-packages] [Bug 1755627] Re: ibrs/ibpb fixes result in excessive kernel logging

[Kamal Mostafa]

** Changed in: linux (Ubuntu Trusty)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

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

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

Title:
  ibrs/ibpb fixes result in excessive kernel logging

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Since at least kernel 4.4.0-116, every invocation of `sysctl -a`
  results in kernel logs similar to the following:

  % sysctl -a &>/dev/null; dmesg -T | tail -8
  [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0

  The output varies with the number of CPUs.

  After digging a bit, it turns out this is triggered upon every read of
  `kernel.ibrs_dump`:

  % for i in {1..3}; do sysctl kernel.ibrs_dump; dmesg -T | tail -8; echo; 
sleep 1; done
  kernel.ibrs_dump = 0
  [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0

  kernel.ibrs_dump = 0
  [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0

  kernel.ibrs_dump = 0
  [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0

  
  Those tests were against an EC2 instance running Ubuntu 4.4.0-116.140-generic 
4.4.98 per /proc/version_signature

  Normally this would not be the biggest concern but we have tooling
  that gathers instance info on a schedule, including sysctl output,
  thus resulting in the kernel ring buffer being full of nothing but
  said output in most cases and hindering live troubleshooting as a
  result.

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

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

[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

[Seth Forshee]

Applied the backport to bionic/master-next, thanks!

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

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1760650] Re: test_074_config_security_default_mmap_min_addr in kernel security test failed with 4.4/4.15 kvm

[Steve Beattie]

Hi, this looks to be a legit bug in how the linux-kvm kernel is derived
from the generic kernel. Examining the annotations file in the linux-kvm
master-next tree:

  https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
kvm/tree/debian.master/config/annotations?h=master-next#n9480

we can see that CONFIG_DEFAULT_MMAP_MIN_ADDR is supposed to be set to
65536 for amd64, etc. However, the generated config for the linux-kvm
kernel contains CONFIG_DEFAULT_MMAP_MIN_ADDR=4096:

  https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
kvm/tree/debian.kvm/config/config.common.ubuntu?h=master-next#n532

So something has gone wrong in generating the linux-kvm kernel.

Thanks.

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

Title:
  test_074_config_security_default_mmap_min_addr in kernel security test
  failed with 4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New

Bug description:
FAIL: test_074_config_security_default_mmap_min_addr 
(__main__.KernelSecurityTest)
CONFIG_DEFAULT_MMAP_MIN_ADDR
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 832, in 
test_074_config_security_default_mmap_min_addr
self.assertEqual(self._get_config(config), expected)
AssertionError: '4096' != '65536'

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:13:02 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760650/+subscriptions

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

[Kernel-packages] [Bug 1758910] Re: Important Kernel fixes to be backported for Power9 (kvm)

[Seth Forshee]

It looks like we've already applied
ff6781fd1bb404d8a551c02c35c70cec1da17ff1 and
e4b79900222b8cccd4da4a7a89581f0e1b764ed2 from other bugs. So now we're
only missing the backport of a5d4b5891c2f1f865a2def1eb0030f534e77ff86.

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

Title:
  Important Kernel fixes to be backported for Power9 (kvm)

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

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-03-26 
02:18:44 ==
  ---Problem Description---
  Important Kernel fixes to be backported for Power9 (kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-13-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Following upstream patches are need to be backported for Power9 KVM to 
function well.

  * Emulation of VMX loads and stores for MMIO.
   
  09f984961c13 KVM: PPC: Book3S: Add MMIO emulation for VMX instructions
  6df3877fc962 KVM: PPC: Book3S: Fix compile error that occurs with some gcc 
versions (needed once 09f984961c13 is in)
   
  * Other important fixes.
   
  05f2bb0313a2 KVM: PPC: Book3S HV: Fix handling of secondary HPTEG in HPT 
resizing code
  790a9df5fbef KVM: PPC: Book3S HV: Make HPT resizing work on POWER9
  a8b48a4dccea KVM: PPC: Book3S HV: Fix trap number return from 
__kvmppc_vcore_entry

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=ff6781fd1bb404d8a551c02c35c70cec1da17ff1
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=e4b79900222b8cccd4da4a7a89581f0e1b764ed2
  and
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=a5d4b5891c2f1f865a2def1eb0030f534e77ff86

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1757497] Re: Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe)

[Seth Forshee]

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

Title:
  Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
  namespaces  (Bolt / NVMe)

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 Committed

Bug description:
  ---Problem Description---
  We are seeing similar IO Hang on some namespaces when running HTX 16 
namespaces on Ubuntu18.04 
   
  ---uname output---
  Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  (Bolt / NVMe)0003:01:00.0 Non-Volatile memory controller [0108]: Samsung 
Electronics Co Ltd NVMe SSD Controller 172Xa [144d:a822] (rev 01)

  Machine Type = AC922 
   
  ---Steps to Reproduce---
   1> Install Ubuntu18.04 , upgrade to 4.15.0-10 kernel
  2> Install htxubuntu-472.deb
  3> make sure you create name spaces 
  #!/bin/bash

  device=/dev/nvme0
  echo $device

  nvme format $device

  nvme set-feature $device -f 0x0b --value=0x0100

  nvme delete-ns $device -n 0x
  sleep 5
  nvme list

  nvme get-log $device -l 200 -i 4

  max=`nvme id-ctrl $device | grep ^nn | awk '{print $NF}'`

  for i in $(eval echo {1..$max})
  do
  echo $i
  nvme create-ns $device --nsze=700 --ncap=700 --flbas=0 --dps=0
  nvme attach-ns $device --namespace-id=$i --controllers=`nvme list-ctrl 
$device | awk -F: '{print $2}'`
  sleep 2
  nvme get-log $device -l 200 -i 4
  sleep 2
  done
  nvme list

  3> run mdt.hd on those namespaces
   
  Contact Information = naveed...@in.ibm.com 
   
  Stack trace output:
   -

  -
  Device id:/dev/nvme0n8  
  Timestamp:Feb 20 16:57:30 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018   
  err=
  sev=1
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519163856; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x8161
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  ** Threshold of 1800 secs on one or more I/Os exceeded!
  0x5ae08b 8 7e0457eaf180  44800 

 
  -

  -
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n4  
  Timestamp:Feb 20 17:14:19 2018   
  err=
  sev=4
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519164859; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x815b
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  0x398a7e 2 71d5a180  33000 

 
  -

  [17643.202114] INFO: task hxestorage:39744 blocked for more than 120 seconds.
  [17643.202180]   Not tainted 4.15.0-10-generic #11-Ubuntu
  [17643.202224] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [17643.202342] hxestorage  D0 

[Kernel-packages] [Bug 1757497] Re: Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe)

[Frank Heimes]

** Changed in: ubuntu-power-systems
   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/1757497

Title:
  Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
  namespaces  (Bolt / NVMe)

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 Committed

Bug description:
  ---Problem Description---
  We are seeing similar IO Hang on some namespaces when running HTX 16 
namespaces on Ubuntu18.04 
   
  ---uname output---
  Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  (Bolt / NVMe)0003:01:00.0 Non-Volatile memory controller [0108]: Samsung 
Electronics Co Ltd NVMe SSD Controller 172Xa [144d:a822] (rev 01)

  Machine Type = AC922 
   
  ---Steps to Reproduce---
   1> Install Ubuntu18.04 , upgrade to 4.15.0-10 kernel
  2> Install htxubuntu-472.deb
  3> make sure you create name spaces 
  #!/bin/bash

  device=/dev/nvme0
  echo $device

  nvme format $device

  nvme set-feature $device -f 0x0b --value=0x0100

  nvme delete-ns $device -n 0x
  sleep 5
  nvme list

  nvme get-log $device -l 200 -i 4

  max=`nvme id-ctrl $device | grep ^nn | awk '{print $NF}'`

  for i in $(eval echo {1..$max})
  do
  echo $i
  nvme create-ns $device --nsze=700 --ncap=700 --flbas=0 --dps=0
  nvme attach-ns $device --namespace-id=$i --controllers=`nvme list-ctrl 
$device | awk -F: '{print $2}'`
  sleep 2
  nvme get-log $device -l 200 -i 4
  sleep 2
  done
  nvme list

  3> run mdt.hd on those namespaces
   
  Contact Information = naveed...@in.ibm.com 
   
  Stack trace output:
   -

  -
  Device id:/dev/nvme0n8  
  Timestamp:Feb 20 16:57:30 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018   
  err=
  sev=1
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519163856; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x8161
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  ** Threshold of 1800 secs on one or more I/Os exceeded!
  0x5ae08b 8 7e0457eaf180  44800 

 
  -

  -
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n4  
  Timestamp:Feb 20 17:14:19 2018   
  err=
  sev=4
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519164859; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x815b
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  0x398a7e 2 71d5a180  33000 

 
  -

  [17643.202114] INFO: task hxestorage:39744 blocked for more than 120 seconds.
  [17643.202180]   Not tainted 4.15.0-10-generic #11-Ubuntu
  [17643.202224] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [17643.202342] hxestorage  D0 

[Kernel-packages] [Bug 1759314] Re: missing memory (32Gib instead of 64GiB)

[Joseph Salisbury]

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

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

Title:
  missing memory (32Gib instead of 64GiB)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The box has 64GiB ram, EFI shell and dmidecode --type memory see 4 x
  16384 MiB, but dmesg and free report 32GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Tue Mar 27 17:48:32 2018
  HibernationDevice: RESUME=/dev/mapper/s02--vg-swap_1
  InstallationDate: Installed on 2018-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  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: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.20
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd04/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial

[Joseph Salisbury]

Thanks for testing.  We now know this bug also exists upstream.  Do you
happen to know if this is a regression?  Was there a prior kernel
version that did not exhibit this bug?

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

Title:
  Intel NICs not properly reporting link speed in SysFS in Xenial

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Triaged

Bug description:
  This was discovered during certification testing of 16.04.4 (I've now
  seen this behaviour at least 2 times)

  A system under test has a 2 port Intel X550 NIC (10Gb)

  Udev reports the NIC as this:
  Category: NETWORK
  Interface: enp94s0f0
  Product: Ethernet Controller 10G X550T
  Vendor: Intel Corporation
  Driver: ixgbe (ver: 5.1.0-k)
  Path: /devices/pci:5d/:5d:00.0/:5e:00.0
  ID:   [8086:1563]
  Subsystem ID: [152d:8a13]

  Ethtool shows this info (this is for the second port, which has the issue)
  Settings for enp94s0f1:
   Supported ports: [ TP ]
   Supported link modes:   100baseT/Full
   1000baseT/Full
   1baseT/Full
   Supported pause frame use: Symmetric
   Supports auto-negotiation: Yes
   Advertised link modes:  100baseT/Full
   1000baseT/Full
   1baseT/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Speed: 1Mb/s
   Duplex: Full
   Port: Twisted Pair
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   MDI-X: Unknown
   Supports Wake-on: umbg
   Wake-on: g
   Current message level: 0x0007 (7)
    drv probe link
   Link detected: yes

  Note ethtool shows an active 10Gb link.

  The test tool determines the NIC speed by introspecting the sysfs data
  for each NIC port.  In this case, by looking at
  /sys/class/net/DEVICENAME/speed

  I've now seen this on a couple different NICs using the ixgbe driver.
  The first port will properly show connected link speed in
  /sys/class/net/DEVICENAME/speed but the second port shows -1 in that
  file.

  Because of this, certification tests are failing because the tool
  believes that the link speed is incorrect.

  This current example is using kernel 4.13.0-37.42~16.04.1

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

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

[Kernel-packages] [Bug 1760876] Re: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build

[Seth Forshee]

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

Title:
  fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel
  module failed to build

Status in fwts package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Was installing the kernel 4.15.0-14-generic when that crash happened.
  Now libelf-dev is requested and need to be added as a dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 15:39:06 2018
  PackageVersion: 18.03.00-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fwts
  Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms 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/fwts/+bug/1760876/+subscriptions

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

[Kernel-packages] [Bug 1759791] Re: NFS + sec=krb5 is broken

[Joseph Salisbury]

Bionic revert request:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091347.html

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

Title:
  NFS + sec=krb5 is broken

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

Bug description:
  I am testing the development branch of Bionic Beaver.
  With the latest update to kernel 4.15.0-13 my nfs-mounts in a university 
network are broken.

  > sudo mount -vvv -t nfs4 my_server:/my/share  /nfs -osoft,sec=krb5
  > mount.nfs4: timeout set for Mon Mar 26 16:29:56 2018
  > mount.nfs4: trying text-based options 
'soft,sec=krb5,nfsvers=4.0,addr=10.162.229.2,clientaddr=10.152.249.189'
  > mount.nfs4: mount(2): Input/output error
  > mount.nfs4: mount system call failed

  > kernel: NFS: nfs4_discover_server_trunking unhandled error -5. Exiting with 
error EIO
  > kernel: RPC: couldn't encode RPC header, exit EIO
  > kernel: gss_marshal: gss_get_mic FAILED (851968)

  
  Known good version: linux-image-4.15.0-10

  I think it is the same bug like in 
https://bugzilla.redhat.com/show_bug.cgi?id=1558977
  The bug was introduced in the mainline kernel 4.15.4 with commit 
"[46e8d06e423c4f35eac7a8b677b713b3ec9b0684] crypto: hash - prevent using keyed 
hashes without setting key"

  This bug should be fixed before releasing ubuntu18.04 by either reverting the 
commit or using a fixed mainline kernel.
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1340 F pulseaudio
   /dev/snd/controlC0:  gdm1340 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-22 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046a:b091 Cherry GmbH 
   Bus 001 Device 002: ID 0bf8:101e Fujitsu Siemens Computers 
   Bus 001 Device 004: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO D757
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=463c4c1b-7771-40dd-833f-f4d68a5fd914 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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:
   
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UnreportableReason: Der Bericht gehört zu einem nicht installierten Paket.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 10/12/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.14.0 for D3531-A1x
  dmi.board.name: D3531-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3531-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.14.0forD3531-A1x:bd10/12/2017:svnFUJITSU:pnESPRIMOD757:pvr:rvnFUJITSU:rnD3531-A1:rvrS26361-D3531-A1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: ESPRIMO-FTS
  dmi.product.name: ESPRIMO D757
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1757497] Re: Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe)

[Joseph Salisbury]

Bionic request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091346.html

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

Title:
  Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
  namespaces  (Bolt / NVMe)

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

Bug description:
  ---Problem Description---
  We are seeing similar IO Hang on some namespaces when running HTX 16 
namespaces on Ubuntu18.04 
   
  ---uname output---
  Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  (Bolt / NVMe)0003:01:00.0 Non-Volatile memory controller [0108]: Samsung 
Electronics Co Ltd NVMe SSD Controller 172Xa [144d:a822] (rev 01)

  Machine Type = AC922 
   
  ---Steps to Reproduce---
   1> Install Ubuntu18.04 , upgrade to 4.15.0-10 kernel
  2> Install htxubuntu-472.deb
  3> make sure you create name spaces 
  #!/bin/bash

  device=/dev/nvme0
  echo $device

  nvme format $device

  nvme set-feature $device -f 0x0b --value=0x0100

  nvme delete-ns $device -n 0x
  sleep 5
  nvme list

  nvme get-log $device -l 200 -i 4

  max=`nvme id-ctrl $device | grep ^nn | awk '{print $NF}'`

  for i in $(eval echo {1..$max})
  do
  echo $i
  nvme create-ns $device --nsze=700 --ncap=700 --flbas=0 --dps=0
  nvme attach-ns $device --namespace-id=$i --controllers=`nvme list-ctrl 
$device | awk -F: '{print $2}'`
  sleep 2
  nvme get-log $device -l 200 -i 4
  sleep 2
  done
  nvme list

  3> run mdt.hd on those namespaces
   
  Contact Information = naveed...@in.ibm.com 
   
  Stack trace output:
   -

  -
  Device id:/dev/nvme0n8  
  Timestamp:Feb 20 16:57:30 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018   
  err=
  sev=1
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519163856; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x8161
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  ** Threshold of 1800 secs on one or more I/Os exceeded!
  0x5ae08b 8 7e0457eaf180  44800 

 
  -

  -
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n4  
  Timestamp:Feb 20 17:14:19 2018   
  err=
  sev=4
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519164859; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x815b
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  0x398a7e 2 71d5a180  33000 

 
  -

  [17643.202114] INFO: task hxestorage:39744 blocked for more than 120 seconds.
  [17643.202180]   Not tainted 4.15.0-10-generic #11-Ubuntu
  [17643.202224] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [17643.202342] hxestorage  D  

[Kernel-packages] [Bug 1757497] Re: Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe)

[Frank Heimes]

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

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

Title:
  Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
  namespaces  (Bolt / NVMe)

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

Bug description:
  ---Problem Description---
  We are seeing similar IO Hang on some namespaces when running HTX 16 
namespaces on Ubuntu18.04 
   
  ---uname output---
  Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  (Bolt / NVMe)0003:01:00.0 Non-Volatile memory controller [0108]: Samsung 
Electronics Co Ltd NVMe SSD Controller 172Xa [144d:a822] (rev 01)

  Machine Type = AC922 
   
  ---Steps to Reproduce---
   1> Install Ubuntu18.04 , upgrade to 4.15.0-10 kernel
  2> Install htxubuntu-472.deb
  3> make sure you create name spaces 
  #!/bin/bash

  device=/dev/nvme0
  echo $device

  nvme format $device

  nvme set-feature $device -f 0x0b --value=0x0100

  nvme delete-ns $device -n 0x
  sleep 5
  nvme list

  nvme get-log $device -l 200 -i 4

  max=`nvme id-ctrl $device | grep ^nn | awk '{print $NF}'`

  for i in $(eval echo {1..$max})
  do
  echo $i
  nvme create-ns $device --nsze=700 --ncap=700 --flbas=0 --dps=0
  nvme attach-ns $device --namespace-id=$i --controllers=`nvme list-ctrl 
$device | awk -F: '{print $2}'`
  sleep 2
  nvme get-log $device -l 200 -i 4
  sleep 2
  done
  nvme list

  3> run mdt.hd on those namespaces
   
  Contact Information = naveed...@in.ibm.com 
   
  Stack trace output:
   -

  -
  Device id:/dev/nvme0n8  
  Timestamp:Feb 20 16:57:30 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018   
  err=
  sev=1
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519163856; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x8161
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  ** Threshold of 1800 secs on one or more I/Os exceeded!
  0x5ae08b 8 7e0457eaf180  44800 

 
  -

  -
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n4  
  Timestamp:Feb 20 17:14:19 2018   
  err=
  sev=4
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519164859; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x815b
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  0x398a7e 2 71d5a180  33000 

 
  -

  [17643.202114] INFO: task hxestorage:39744 blocked for more than 120 seconds.
  [17643.202180]   Not tainted 4.15.0-10-generic #11-Ubuntu
  [17643.202224] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [17643.202342] hxestorage  D0 39744   3424 

[Kernel-packages] [Bug 1757497] Re: Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16 namespaces (Bolt / NVMe)

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

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

Title:
  Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
  namespaces  (Bolt / NVMe)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---
  We are seeing similar IO Hang on some namespaces when running HTX 16 
namespaces on Ubuntu18.04 
   
  ---uname output---
  Linux ltciofvtr-spoon4 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  (Bolt / NVMe)0003:01:00.0 Non-Volatile memory controller [0108]: Samsung 
Electronics Co Ltd NVMe SSD Controller 172Xa [144d:a822] (rev 01)

  Machine Type = AC922 
   
  ---Steps to Reproduce---
   1> Install Ubuntu18.04 , upgrade to 4.15.0-10 kernel
  2> Install htxubuntu-472.deb
  3> make sure you create name spaces 
  #!/bin/bash

  device=/dev/nvme0
  echo $device

  nvme format $device

  nvme set-feature $device -f 0x0b --value=0x0100

  nvme delete-ns $device -n 0x
  sleep 5
  nvme list

  nvme get-log $device -l 200 -i 4

  max=`nvme id-ctrl $device | grep ^nn | awk '{print $NF}'`

  for i in $(eval echo {1..$max})
  do
  echo $i
  nvme create-ns $device --nsze=700 --ncap=700 --flbas=0 --dps=0
  nvme attach-ns $device --namespace-id=$i --controllers=`nvme list-ctrl 
$device | awk -F: '{print $2}'`
  sleep 2
  nvme get-log $device -l 200 -i 4
  sleep 2
  done
  nvme list

  3> run mdt.hd on those namespaces
   
  Contact Information = naveed...@in.ibm.com 
   
  Stack trace output:
   -

  -
  Device id:/dev/nvme0n8  
  Timestamp:Feb 20 16:57:30 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018   
  err=
  sev=1
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519163856; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x8161
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  ** Threshold of 1800 secs on one or more I/Os exceeded!
  0x5ae08b 8 7e0457eaf180  44800 

 
  -

  -
  Device id:/dev/nvme0n10 
  Timestamp:Feb 20 16:57:36 2018
  err=
  sev=1
  Exerciser Name:hxestorage
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available
  Device:Not Available
  Error Text:Hardware Exerciser stopped on error

  
  -

  - 
  
  Device id:/dev/nvme0n4  
  Timestamp:Feb 20 17:14:19 2018   
  err=
  sev=4
  Exerciser Name:hxestorage   
  Serial No:Not Available
  Part No:Not Available
  Location:Not Available
  FRU Number:Not Available   
  Device:Not Available
  Error Text:Hung I/O alert! Segment table-1,  Detected 1 I/O(s) hung.
  Current time: 1519164859; hang criteria: 600 secs, Hard hang threshold: 3
  Process ID: 0x815b
 1st lba   Blocks   KernelHang   Duration
  (Hex)(Hex)ThreadCnt(Secs)
  0x398a7e 2 71d5a180  33000 

 
  -

  [17643.202114] INFO: task hxestorage:39744 blocked for more than 120 seconds.
  [17643.202180]   Not tainted 4.15.0-10-generic #11-Ubuntu
  

[Kernel-packages] [Bug 1760653] Re: test_077_config_security_ipsec in kernel security test failed with 4.4/4.15 kvm

[Joseph Salisbury]

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

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

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

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

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

Title:
  test_077_config_security_ipsec in kernel security test failed with
  4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New

Bug description:
FAIL: test_077_config_security_ipsec (__main__.KernelSecurityTest)
Config options for IPsec
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 897, in 
test_077_config_security_ipsec
self.assertTrue(self._test_config(c), 'CONFIG_%s is not set' % (c))
AssertionError: CONFIG_XFRM_USER is not set

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:17:15 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760653/+subscriptions

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

[Kernel-packages] [Bug 1759354] Re: 18.04 After suspend fan goes to max speed on resume, have to reset in bios

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16


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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16


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

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

Title:
  problems with kernel 4.13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop call dc pro. it is made in china. processor is
  Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The
  problems are:

  1 the ubuntu 16.04.03 installation will hang somewhere. luckily
  16.04.02 will go through.

  2 the system will not boot after upgrade to kernel 4.13. the old
  kernel 4.8 will boot without problem.

  3 After install the cuda 9.1 both kernel will boot, but nvidia did not
  come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia
  commands left "nvidia-detector  nvidia-modprobe  nvidia-settings" )
  for the kernel 4.13, the old kernel 4.8 is ok though

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.24
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Feb 27 13:39:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-17 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1760654] Re: test_140_kernel_modules_not_tainted in kernel security test failed with 4.4 X-kvm

[Joseph Salisbury]

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

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

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

Title:
  test_140_kernel_modules_not_tainted in kernel security test failed
  with 4.4 X-kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
FAIL: test_140_kernel_modules_not_tainted (__main__.KernelSecurityTest)
kernel modules are not marked with a taint flag (especially 'E' for 
TAINT_UNSIGNED_MODULE)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1740, in 
test_140_kernel_modules_not_tainted
self.fail('Module \'%s\' is tainted: %s' % (fields[0], last_field))
AssertionError: Module 'signpost' is tainted: (OE)

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:18:25 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760654/+subscriptions

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

[Kernel-packages] [Bug 1760642] Re: test_096_proc_entries_unreadable in kernel security test failed with 4.4 X-kvm

[Joseph Salisbury]

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

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

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

Title:
  test_096_proc_entries_unreadable in kernel security test failed with
  4.4 X-kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
  The test failed with:
ERROR: test_096_proc_entries_unreadable (__main__.KernelSecurityTest)
sensitive files in /proc are not world readable
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1584, in 
test_096_proc_entries_unreadable
self.assertEqual(os.stat(name).st_mode & mask, expected, '%s is world 
readable' % (name))
OSError: [Errno 2] No such file or directory: '/proc/slabinfo'


  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:53:43 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760642/+subscriptions

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

[Kernel-packages] [Bug 1760646] Re: test_072_config_debug_set_module_ronx in kernel security test failed with 4.4 X-kvm

[Joseph Salisbury]

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

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

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

Title:
  test_072_config_debug_set_module_ronx  in kernel security test failed
  with 4.4 X-kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
FAIL: test_072_config_debug_set_module_ronx (__main__.KernelSecurityTest)
CONFIG_DEBUG_SET_MODULE_RONX/CONFIG_STRICT_MODULE_RWX enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 665, in 
test_072_config_debug_set_module_ronx
self.assertEqual(self._test_config(option), expected)
AssertionError: False != True

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:59:18 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760646/+subscriptions

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

[Kernel-packages] [Bug 1760643] Re: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm

[Joseph Salisbury]

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

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

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

Title:
  test_072_config_debug_rodata in kernel security test failed with 4.4
  X-kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
  The test failed with:
FAIL: test_072_config_debug_rodata (__main__.KernelSecurityTest)
CONFIG_DEBUG_RODATA/CONFIG_STRICT_KERNEL_RWX enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 642, in 
test_072_config_debug_rodata
self.assertEqual(self._test_config(option), expected)
AssertionError: False != True

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:54:36 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760643/+subscriptions

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

[Kernel-packages] [Bug 1760649] Re: test_072_strict_devmem in kernel security test failed with 4.4/4.15 kvm

[Joseph Salisbury]

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

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

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

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

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

Title:
  test_072_strict_devmem in kernel security test failed with 4.4/4.15
  kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New

Bug description:
FAIL: test_072_strict_devmem (__main__.KernelSecurityTest)
/dev/mem unreadable for kernel memory
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 766, in test_072_strict_devmem
self.assertTrue(rc in expected, 'exit code: %d (wanted %s). 
Output:\n%s' % (rc, ", ".join(["%d" % (x) for x in expected]), output))
AssertionError: exit code: 1 (wanted 0). Output:
/dev/mem: No such file or directory

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:10:38 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760649/+subscriptions

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

[Kernel-packages] [Bug 1760647] Re: Unable to build lttng module on 4.4 X-KVM

[Joseph Salisbury]

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

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

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

Title:
  Unable to build lttng module on 4.4 X-KVM

Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
  Tested with the lttng module in -proposed (2.8.0-1ubuntu1~16.04.5), it
  looks like this is the CONFIG issue.

  Build log:

  DKMS make.log for lttng-modules-2.8.0 for kernel 4.4.0-1019-kvm (x86_64)
  Mon Apr  2 17:05:48 UTC 2018
  make: Entering directory '/usr/src/linux-headers-4.4.0-1019-kvm'
  /var/lib/dkms/lttng-modules/2.8.0/build/Makefile:12: *** The option 
CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration.  Stop.
  Makefile:1423: recipe for target 
'_module_/var/lib/dkms/lttng-modules/2.8.0/build' failed
  make: *** [_module_/var/lib/dkms/lttng-modules/2.8.0/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.4.0-1019-kvm'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:38:25 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1760648] Re: test_072_config_strict_devmem in kernel security test failed with 4.4/4.15 kvm

[Joseph Salisbury]

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

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

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

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

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

Title:
  test_072_config_strict_devmem in kernel security test failed with
  4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New

Bug description:
FAIL: test_072_config_strict_devmem (__main__.KernelSecurityTest)
CONFIG_STRICT_DEVMEM enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 707, in 
test_072_config_strict_devmem
self.assertEqual(self._test_config('STRICT_DEVMEM'), strict)
AssertionError: False != True

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:02:10 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760648/+subscriptions

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

[Kernel-packages] [Bug 1760652] Re: test_076_config_security_acl_ext4 in kernel security test failed with 4.4/4.15 kvm

[Joseph Salisbury]

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

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

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

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

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

Title:
  test_076_config_security_acl_ext4  in kernel security test failed with
  4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New

Bug description:
FAIL: test_076_config_security_acl_ext4 (__main__.KernelSecurityTest)
CONFIG_EXT4_FS_SECURITY set (LP: #1295948)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 876, in 
test_076_config_security_acl_ext4
self.assertTrue(self._test_config('EXT4_FS_SECURITY'), 
'CONFIG_EXT4_FS_SECURITY is not set')
AssertionError: CONFIG_EXT4_FS_SECURITY is not set


  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:13:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760652/+subscriptions

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

[Kernel-packages] [Bug 1760650] Re: test_074_config_security_default_mmap_min_addr in kernel security test failed with 4.4/4.15 kvm

[Joseph Salisbury]

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

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

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

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

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

Title:
  test_074_config_security_default_mmap_min_addr in kernel security test
  failed with 4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New

Bug description:
FAIL: test_074_config_security_default_mmap_min_addr 
(__main__.KernelSecurityTest)
CONFIG_DEFAULT_MMAP_MIN_ADDR
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 832, in 
test_074_config_security_default_mmap_min_addr
self.assertEqual(self._get_config(config), expected)
AssertionError: '4096' != '65536'

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:13:02 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760650/+subscriptions

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

[Kernel-packages] [Bug 1760656] Re: test_151_sysctl_disables_bpf_unpriv_userns in kernel security test failed with 4.4/4.15 kvm

[Joseph Salisbury]

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

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

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

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

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

Title:
  test_151_sysctl_disables_bpf_unpriv_userns in kernel security test
  failed with 4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New

Bug description:
FAIL: test_151_sysctl_disables_bpf_unpriv_userns 
(__main__.KernelSecurityTest)
unprivileged_bpf_disabled sysctl supported
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1951, in 
test_151_sysctl_disables_bpf_unpriv_userns
self._test_sysctl_value('kernel/unprivileged_bpf_disabled', expected, 
exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1185, in _test_sysctl_value
self.assertEqual(exists, os.path.exists(sysctl), sysctl)
AssertionError: /proc/sys/kernel/unprivileged_bpf_disabled

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:22:38 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760656/+subscriptions

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