[Kernel-packages] [Bug 1744580] Re: 4.4.0-109 kernel panic upon boot with AMD Athlon II X3 455

2018-01-23 Thread Sebastian K. 
Upgrading to -112 solved the problem. No more kernel panics upon boot.

Thank you!

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

Title:
  4.4.0-109 kernel panic upon boot with AMD Athlon II X3 455

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 4.4.0-109, the system won't boot any more.

  At the first boot tentative, the following message is shown and the system 
freezes:
  "Failure reading sector 0xbbcfd0 from hd0"

  Upon retry, a kernel panic is shown (see attached screen hard copy)

  Going back to 4.4.0-104.127-generic solved the problem.

  I've been able to reproduce this bug in a consistent way: I tried
  several times to go boot into 4.0.0-109 and the system froze with the
  described behaviour, but booting into 4.0.0-104 always worked.

  I have checked the bug reports concerning kernel panic after upgrade
  to 4.4.0-108, but this problem seems to be different: I experience
  this problem after upgrading to 4.4.0-109, which presumably fixed the
  problem reported the other bug reports (I don't know if my
  configuration would've worked with 108, because I have not updated
  during a week)

  $ cat /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 16
  model : 5
  model name: AMD Athlon(tm) II X3 455 Processor
  stepping  : 3
  microcode : 0x1c8
  cpu MHz   : 800.000
  cache size: 512 KB
  physical id   : 0
  siblings  : 3
  core id   : 0
  cpu cores : 3
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 5
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni 
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate vmmcall npt 
lbrv svm_lock nrip_save
  bugs  : tlb_mmatch fxsave_leak sysret_ss_attrs
  bogomips  : 6629.24
  TLB size  : 1024 4K pages
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 48 bits physical, 48 bits virtual
  power management: ts ttp tm stc 100mhzsteps hwpstate
  [... and two more identical cpus]
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   1879 F pulseaudio
   /dev/snd/controlC2:  administrator   1879 F pulseaudio
   /dev/snd/controlC1:  administrator   1879 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=4483f480-1b20-4b71-8f19-8ae0b8239101
  InstallationDate: Installed on 2012-08-21 (1979 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=765c1614-0bec-4d44-b970-139e13f9f135 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 02/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd02/20/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

2018-01-23 Thread Frank Heimes 
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Tags added: triage-g

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

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

** Tags added: triage-g

** Tags added: kernel-da-key

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

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

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70]

[Kernel-packages] [Bug 1745104] [NEW] ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

2018-01-23 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

== Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 ==
root@boslcp4g5:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@boslcp4g5:~# uname -r
4.13.0-25-generic
root@boslcp4g5:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
   /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-25-generic
kdump initrd:
   /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
current state:ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@boslcp4g5:~# kdump-config status
current state   : ready to kdump
root@boslcp4g5:~# echo c > /proc/sysrq-trigger
[  176.911191] sysrq: SysRq : This sysrq operation is disabled.
root@boslcp4g5:~# sysctl -w kernel.sysrq=1
kernel.sysrq = 1
root@boslcp4g5:~# echo c > /proc/sysrq-trigger
[  240.304466] sysrq: SysRq : Trigger a crash
[  240.304545] Unable to handle kernel paging request for data at address 
0x
[  240.304656] Faulting instruction address: 0xc0792f88
[  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
[  240.304846] SMP NR_CPUS=2048
[  240.304848] NUMA
[  240.304903] pSeries
[  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
[  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
[  240.305886] task: c000ff904500 task.stack: c001f2d7c000
[  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: c0792f60
[  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
[  240.306195] MSR: 80009033 
[  240.306207]   CR: 2842  XER: 2004
[  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
[  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
[  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
[  240.306338] GPR08: 0007 0001  

[  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
[  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
[  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
[  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
[  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
[  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
[  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
[  240.307553] Call Trace:
[  240.307594] [c001f2d7fc70] [c0793e98] __handle_sysrq+0xd8/0x2b0 
(unreliable)
[  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
[  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
[  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
[  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
[  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
[  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
[  240.308340] Instruction dump:
[  240.308400] 4bfff9f1 4bfffe50 3c4c00e6 384232a0 7c0802a6 6000 3921 
3d42001d
[  240.308522] 394adab0 912a 7c0004ac 3940 <992a> 4e800020 3c4c00e6 
38423270
[  240.308644] ---[ end trace 97aaa45518689ad0 ]---
[  240.314197]
[  240.314408] Sending IPI to other CPUs
[  240.357424] IPI complete
[  240.377038] kexec: Starting switchover sequence.
   it stops here.

== Comment: #2 - MAMATHA INAMDAR  - 2018-01-24 01:07:12 ==
Hi Chanh,

We need following patch which will fix this issue. I think this patch is
not integrated in 18.04 kernel

>From 2621e945fbf1d6df5f3f0ba7be5bae3d2cf9b6a5 Mon Sep 17 00:00:00 2001
From: Michael Ellerman

[Kernel-packages] [Bug 1733990] Re: package linux-headers-4.13.0-18 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-18/drivers/clk/mvebu/Kconfig.dpkg-new': Ope

2018-01-23 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-headers-4.13.0-18 (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-4.13.0-18/drivers/clk/mvebu/Kconfig.dpkg-new': Operation not
  permitted

Status in linux package in Ubuntu:
  Expired

Bug description:
  ran updates from ubuntu got sent here

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-18 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  doc2643 F pulseaudio
   /dev/snd/controlC1:  doc2643 F pulseaudio
  Date: Wed Nov 22 18:47:50 2017
  DuplicateSignature:
   package:linux-headers-4.13.0-18:(not installed)
   Unpacking linux-headers-4.13.0-18 (4.13.0-18.21) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ILGEQz/16-linux-headers-4.13.0-18_4.13.0-18.21_all.deb 
(--unpack):
unable to open 
'/usr/src/linux-headers-4.13.0-18/drivers/clk/mvebu/Kconfig.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-4.13.0-18/drivers/clk/mvebu/Kconfig.dpkg-new': 
Operation not permitted
  HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
  InstallationDate: Installed on 2016-01-18 (674 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: EVGA 122-CK-NF68
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.13.0-18 (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-4.13.0-18/drivers/clk/mvebu/Kconfig.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 122-CK-NF68
  dmi.board.vendor: EVGA
  dmi.board.version: 2
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA
  dmi.chassis.version: 122-CK-NF68
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68:
  dmi.product.name: 122-CK-NF68
  dmi.product.version: 2
  dmi.sys.vendor: EVGA

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

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

[Kernel-packages] [Bug 1734099] Re: tcp_input.c:2826 tcp_fastretrans_alert+0x7d0/0x990

2018-01-23 Thread Launchpad Bug Tracker 
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  tcp_input.c:2826 tcp_fastretrans_alert+0x7d0/0x990

Status in linux package in Ubuntu:
  Expired

Bug description:
  Server reboot after multiple errors in dmesg:

  [80484.782020] [ cut here ]
  [80484.782043] WARNING: CPU: 0 PID: 0 at 
/build/linux-KM2a5S/linux-4.13.0/net/ipv4/tcp_input.c:2826 
tcp_fastretrans_alert+0x7d0/0x990
  [80484.782045] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs 
vhost_net vhost tap ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables 
iscsi_target_mod target_core_mod fcoe libfcoe libfc scsi_transport_fc 
hangcheck_timer xt_CHECKSUM xt_multiport ip6table_filter ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat ip6table_mangle ip6_tables xt_limit 
xt_NFLOG nfnetlink_log xt_physdev br_netfilter xt_comment xt_conntrack 
iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_REDIRECT 
nf_nat_redirect iptable_nat xt_tcpudp xt_mark 8021q garp mrp bridge xt_DSCP stp 
llc xt_owner iptable_mangle openvswitch nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink binfmt_misc dm_thin_pool 
dm_persistent_data dm_bio_prison
  [80484.782074]  dm_bufio xfs amd64_edac_mod edac_mce_amd kvm_amd kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd zfs(PO) glue_helper cryptd zunicode(PO) zavl(PO) 
zcommon(PO) znvpair(PO) eeepc_wmi asus_wmi sparse_keymap video wmi_bmof 
uvcvideo fam15h_power k10temp videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev spl(O) media i2c_piix4 snd_usb_audio snd_usbmidi_lib 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm joydev input_leds snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore 
shpchp mac_hid dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua tcp_htcp cuse 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp
  [80484.782113]  libiscsi nfsd scsi_transport_iscsi auth_rpcgss sbs sbshc 
nfs_acl lockd max6650 grace it87 hwmon_vid asus_atk0110 aoe sunrpc ip_tables 
x_tables autofs4 btrfs raid10 raid1 raid0 multipath linear raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c amdkfd amd_iommu_v2 radeon i2c_algo_bit hid_generic ttm 
drm_kms_helper e1000e firewire_ohci uas syscopyarea sysfillrect ptp 
firewire_core usbhid sysimgblt r8169 mxm_wmi usb_storage crc_itu_t fb_sys_fops 
mii hid pps_core drm ahci libahci wmi
  [80484.782142] CPU: 0 PID: 0 Comm: swapper/0 Tainted: PW  O
4.13.0-17-generic #20-Ubuntu
  [80484.782143] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./SABERTOOTH 990FX, BIOS 1604 10/16/2012
  [80484.782145] task: 86a10480 task.stack: 86a0
  [80484.782147] RIP: 0010:tcp_fastretrans_alert+0x7d0/0x990
  [80484.782149] RSP: 0018:97b23ec03940 EFLAGS: 00010202
  [80484.782150] RAX:  RBX: 97aa03b65800 RCX: 
97b23ec039a4
  [80484.782152] RDX: 0001 RSI: 0002 RDI: 
97aa03b65800
  [80484.782153] RBP: 97b23ec03980 R08:  R09: 

  [80484.782154] R10:  R11:  R12: 
5120
  [80484.782156] R13: 97b23ec039ac R14: 0001 R15: 
97b23ec039a4
  [80484.782157] FS:  () GS:97b23ec0() 
knlGS:
  [80484.782159] CS:  0010 DS:  ES:  CR0: 80050033
  [80484.782160] CR2: 7f121094e000 CR3: 0003bb7ca000 CR4: 
000406f0
  [80484.782162] Call Trace:
  [80484.782164]  
  [80484.782169]  ? sk_reset_timer+0x18/0x30
  [80484.782171]  tcp_ack+0x4ee/0x890
  [80484.782173]  tcp_rcv_established+0x323/0x770
  [80484.782176]  tcp_v4_do_rcv+0x90/0x1e0
  [80484.782178]  tcp_v4_rcv+0x92b/0x9d0
  [80484.782181]  ip_local_deliver_finish+0x5c/0x1f0
  [80484.782182]  ip_local_deliver+0x6f/0xe0
  [80484.782184]  ? ip_rcv_finish+0x410/0x410
  [80484.782186]  ip_rcv_finish+0x120/0x410
  [80484.782188]  ip_rcv+0x28c/0x3a0
  [80484.782190]  ? inet_del_offload+0x40/0x40
  [80484.782192]  __netif_receive_skb_core+0x39a/0xaa0
  [80484.782195]  ? find_busiest_group+0x47/0x4a0
  [80484.782197]  __netif_receive_skb+0x18/0x60
  [80484.782199]  ? __netif_receive_skb+0x18/0x60
  [80484.782201]  netif_receive_skb_internal+0x3f/0x3f0
  [80484.782203]  ? dev_gro_receive+0x2dc/0x480
  [80484.782205]  napi_gro_receive+0xc2/0xe0
  [80484.782214]  e1000_receive_skb+0x86/0xe0 [e1000e]
  [80484.782221]  e1000_clean_rx_irq+0x1fb/0x3d0 [e1000e]
  [80484.782228]

[Kernel-packages] [Bug 1745071] [NEW] Xenial update to 4.4.110 stable release

2018-01-23 Thread Khaled El Mously 
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.110 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.110 stable release shall be
applied:

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-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/1745071

Title:
  Xenial update to 4.4.110 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.110 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.110 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1745069] Re: Xenial update to 4.4.109 stable release

2018-01-23 Thread Khaled El Mously 
The following patches were skipped as they were previously applied:
 * kvm: x86: fix RSM when PCID is non-zero
 * x86/mm: Disable PCID on 32-bit kernels
 * x86/mm: Enable CR4.PCIDE on supported systems

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.109 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.109 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.109 stable release shall be
- applied:
+    The following patches from the 4.4.109 stable release shall be applied:
+ * ACPI: APEI / ERST: Fix missing error handling in erst_reader()
+ * crypto: mcryptd - protect the per-CPU queue with a lock
+ * mfd: cros ec: spi: Don't send first message too soon
+ * mfd: twl4030-audio: Fix sibling-node lookup
+ * mfd: twl6040: Fix child-node lookup
+ * ALSA: rawmidi: Avoid racy info ioctl via ctl device
+ * ALSA: usb-audio: Fix the missing ctl name suffix at parsing SU
+ * PCI / PM: Force devices to D0 in pci_pm_thaw_noirq()
+ * parisc: Hide Diva-built-in serial aux and graphics card
+ * spi: xilinx: Detect stall with Unknown commands
+ * KVM: X86: Fix load RFLAGS w/o the fixed bit
+ * kvm: x86: fix RSM when PCID is non-zero
+ * powerpc/perf: Dereference BHRB entries safely
+ * net: mvneta: clear interface link status on port disable
+ * tracing: Remove extra zeroing out of the ring buffer page
+ * tracing: Fix possible double free on failure of allocating trace buffer
+ * tracing: Fix crash when it fails to alloc ring buffer
+ * ring-buffer: Mask out the info bits when returning buffer page length
+ * iw_cxgb4: Only validate the MSN for successful completions
+ * ASoC: fsl_ssi: AC'97 ops need regmap, clock and cleaning up on failure
+ * ASoC: twl4030: fix child-node lookup
+ * ALSA: hda: Drop useless WARN_ON()
+ * ALSA: hda - fix headset mic detection issue on a Dell machine
+ * x86/vm86/32: Switch to flush_tlb_mm_range() in mark_screen_rdonly()
+ * x86/mm: Remove flush_tlb() and flush_tlb_current_task()
+ * x86/mm: Make flush_tlb_mm_range() more predictable
+ * x86/mm: Reimplement flush_tlb_page() using flush_tlb_mm_range()
+ * x86/mm: Remove the UP asm/tlbflush.h code, always use the (formerly) SMP 
code
+ * x86/mm: Disable PCID on 32-bit kernels
+ * x86/mm: Add the 'nopcid' boot option to turn off PCID
+ * x86/mm: Enable CR4.PCIDE on supported systems
+ * x86/mm/64: Fix reboot interaction with CR4.PCIDE
+ * kbuild: add '-fno-stack-check' to kernel build options
+ * ipv4: igmp: guard against silly MTU values
+ * ipv6: mcast: better catch silly mtu values
+ * net: igmp: Use correct source address on IGMPv3 reports
+ * netlink: Add netns check on taps
+ * net: qmi_wwan: add Sierra EM7565 1199:9091
+ * net: reevalulate autoflowlabel setting after sysctl setting
+ * tcp md5sig: Use skb's saddr when replying to an incoming segment
+ * tg3: Fix rx hang on MTU change with 5717/5719
+ * net: ipv4: fix for a race condition in raw_sendmsg
+ * net: mvmdio: disable/unprepare clocks in EPROBE_DEFER case
+ * sctp: Replace use of sockets_allocated with specified macro.
+ * ipv4: Fix use-after-free when flushing FIB tables
+ * net: bridge: fix early call to br_stp_change_bridge_id and plug newlink 
leaks
+ * net: Fix double free and memory corruption in get_net_ns_by_id()
+ * net: phy: micrel: ksz9031: reconfigure autoneg after phy autoneg workaround
+ * sock: free skb in skb_complete_tx_timestamp on error
+ * usbip: fix usbip bind writing random string after command in match_busid
+ * usbip: stub: stop printing kernel pointer addresses in messages
+ * usbip: vhci: stop printing kernel pointer addresses in messages
+ * USB: serial: ftdi_sio: add id for Airbus DS P8GR
+ * USB: serial: qcserial: add Sierra Wireless EM7565
+ * USB: serial: option: add support for Telit ME910 PID 0x1101
+ * USB: serial: option: adding support for YUGA CLM920-NC5
+ * usb: Add device quirk for Logitech HD Pro Webcam C925e
+ * usb: add RESET_RESUME for ELSA MicroLink 56K
+ * USB: Fix off by one in type-specific length check of BOS SSP

[Kernel-packages] [Bug 1744852] Re: Broken screen after upgrading to 4.13.0-31.34~16.04.1

2018-01-23 Thread la Nube 
I used UKUU to upgrade kernel 4.15.0-rc9.

During upgrading, the following warning messages showed me.

update-initramfs: Generating /boot/initrd.img-4.15.0-041500rc9-generic
W: Possibel missing firmware /lib/firmware/i915/kbl_guc_ver9.14.bin for module 
i915
W: Possibel missing firmware /lib/firmware/i915/bxt_guc_ver8.7.bin for module 
i915

However, after rebooting with 4.15-rc9, screen was not broken. Works
WELL.

'uname -a' says that
Linux asus-1000HE 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 
02:50:29 UTC 2018 i686 i686 i686 GNU/Linux

** Tags added: kernel-fixed-upstream

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

** No longer affects: linux-hwe (Ubuntu)

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

Title:
  Broken screen after upgrading to 4.13.0-31.34~16.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded linux kernel from 4.10.0-42.46~16.04.1 to 4.13.0-31.34~16.04.1.
  After rebooting, my linux screen has been broken.

  See Imgur images.

  https://i.imgur.com/9cXTyIG.jpg
  https://i.imgur.com/0skgISl.jpg

  Restroing kernel 4.10, then works well.
  Also, 4.4.0-112.135 works well.

  --

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.3 LTS
  Release: 16.04
  Codename: xenial
  Linux asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 
UTC 2017 i686 i686 i686 GNU/Linux

  CPU: Single core Intel Atom N270 (-HT-) cache: 512 KB
     flags: (nx pae sse sse2 sse3 ssse3) bmips: 3192
     clock speeds: max: 1600 MHz 1: 1333 MHz 2: 800 MHz

  Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller
     bus-ID: 00:02.0
     Display Server: N/A drivers: intel (unloaded: fbdev,vesa)
     tty size: 80x24 Advanced Data: N/A out of X

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

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

[Kernel-packages] [Bug 1744852] Re: Broken screen after upgrading to 4.13.0-31.34~16.04.1

2018-01-23 Thread la Nube 
Correction.
W: Possibel -> W: Possible

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

Title:
  Broken screen after upgrading to 4.13.0-31.34~16.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded linux kernel from 4.10.0-42.46~16.04.1 to 4.13.0-31.34~16.04.1.
  After rebooting, my linux screen has been broken.

  See Imgur images.

  https://i.imgur.com/9cXTyIG.jpg
  https://i.imgur.com/0skgISl.jpg

  Restroing kernel 4.10, then works well.
  Also, 4.4.0-112.135 works well.

  --

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.3 LTS
  Release: 16.04
  Codename: xenial
  Linux asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 
UTC 2017 i686 i686 i686 GNU/Linux

  CPU: Single core Intel Atom N270 (-HT-) cache: 512 KB
     flags: (nx pae sse sse2 sse3 ssse3) bmips: 3192
     clock speeds: max: 1600 MHz 1: 1333 MHz 2: 800 MHz

  Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller
     bus-ID: 00:02.0
     Display Server: N/A drivers: intel (unloaded: fbdev,vesa)
     tty size: 80x24 Advanced Data: N/A out of X

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

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

[Kernel-packages] [Bug 1745054] Re: Xenial update to 4.4.108 stable release

2018-01-23 Thread Khaled El Mously 
The following patches were NOT applied as they were applied previously:

 * x86/mm: Add INVPCID helpers
 * x86/mm: Build arch/x86/mm/tlb.c even on !SMP
 * x86/mm, sched/core: Uninline switch_mm()
 * r8152: fix the list rx_done may be used without initialization

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

Title:
  Xenial update to 4.4.108 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.108 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.108 stable release shall be applied:
  * arm64: Initialise high_memory global variable earlier
  * cxl: Check if vphb exists before iterating over AFU devices
  * x86/mm: Add INVPCID helpers
  * x86/mm: Fix INVPCID asm constraint
  * x86/mm: Add a 'noinvpcid' boot option to turn off INVPCID
  * x86/mm: If INVPCID is available, use it to flush global mappings
  * mm/rmap: batched invalidations should use existing api
  * mm/mmu_context, sched/core: Fix mmu_context.h assumption
  * sched/core: Add switch_mm_irqs_off() and use it in the scheduler
  * x86/mm: Build arch/x86/mm/tlb.c even on !SMP
  * x86/mm, sched/core: Uninline switch_mm()
  * x86/mm, sched/core: Turn off IRQs in switch_mm()
  * ARM: Hide finish_arch_post_lock_switch() from modules
  * sched/core: Idle_task_exit() shouldn't use switch_mm_irqs_off()
  * x86/irq: Do not substract irq_tlb_count from irq_call_count
  * ALSA: hda - add support for docking station for HP 820 G2
  * ALSA: hda - add support for docking station for HP 840 G3
  * arm: kprobes: Fix the return address of multiple kretprobes
  * arm: kprobes: Align stack to 8-bytes in test code
  * cpuidle: Validate cpu_dev in cpuidle_add_sysfs()
  * r8152: fix the list rx_done may be used without initialization
  * crypto: deadlock between crypto_alg_sem/rtnl_mutex/genl_mutex
  * sch_dsmark: fix invalid skb_cow() usage
  * bna: integer overflow bug in debugfs
  * net: qmi_wwan: Add USB IDs for MDM6600 modem on Motorola Droid 4
  * usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed
  * usb: gadget: udc: remove pointer dereference after free
  * netfilter: nfnl_cthelper: fix runtime expectation policy updates
  * netfilter: nfnl_cthelper: Fix memory leak
  * inet: frag: release spinlock before calling icmp_send()
  * pinctrl: st: add irq_request/release_resources callbacks
  * scsi: lpfc: Fix PT2PT PRLI reject
  * KVM: x86: correct async page present tracepoint
  * KVM: VMX: Fix enable VPID conditions
  * ARM: dts: ti: fix PCI bus dtc warnings
  * hwmon: (asus_atk0110) fix uninitialized data access
  * HID: xinmo: fix for out of range for THT 2P arcade controller.
  * r8152: prevent the driver from transmitting packets with carrier off
  * s390/qeth: no ETH header for outbound AF_IUCV
  * bna: avoid writing uninitialized data into hw registers
  * net: Do not allow negative values for busy_read and busy_poll sysctl 
interfaces
  * i40e: Do not enable NAPI on q_vectors that have no rings
  * RDMA/iser: Fix possible mr leak on device removal event
  * irda: vlsi_ir: fix check for DMA mapping errors
  * netfilter: nfnl_cthelper: fix a race when walk the nf_ct_helper_hash table
  * netfilter: nf_nat_snmp: Fix panic when snmp_trap_helper fails to register
  * ARM: dts: am335x-evmsk: adjust mmc2 param to allow suspend
  * KVM: pci-assign: do not map smm memory slot pages in vt-d page tables
  * isdn: kcapi: avoid uninitialized data
  * xhci: plat: Register shutdown for xhci_plat
  * netfilter: nfnetlink_queue: fix secctx memory leak
  * ARM: dma-mapping: disallow dma_get_sgtable() for non-kernel managed memory
  * cpuidle: powernv: Pass correct drv->cpumask for registration
  * bnxt_en: Fix NULL pointer dereference in reopen failure path
  * backlight: pwm_bl: Fix overflow condition
  * crypto: crypto4xx - increase context and scatter ring buffer elements
  * rtc: pl031: make interrupt optional
  * net: phy: at803x: Change error to EINVAL for invalid MAC
  * PCI: Avoid bus reset if bridge itself is broken
  * scsi: cxgb4i: fix Tx skb leak
  * scsi: mpt3sas: Fix IO error occurs on pulling out a drive from RAID1 volume 
created on two SATA drive
  * PCI: Create SR-IOV virtfn/physfn links before attaching driver
  * igb: check memory allocation failure
  * ixgbe: fix use of uninitialized padding
  * PCI/AER: Report non-fatal errors only to the affected endpoint
  * scsi:

[Kernel-packages] [Bug 1745069] [NEW] Xenial update to 4.4.109 stable release

2018-01-23 Thread Khaled El Mously 
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.109 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.109 stable release shall be
applied:

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-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/1745069

Title:
  Xenial update to 4.4.109 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.109 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.109 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1745068] [NEW] Xenial update to 4.4.109 stable release

2018-01-23 Thread Khaled El Mously 
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.109 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.109 stable release shall be
applied:

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-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/1745068

Title:
  Xenial update to 4.4.109 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.109 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.109 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1744806] Re: Bluetooth is turned off at boot with latest update (bluez 5.37-0ubuntu5.2)

2018-01-23 Thread Daniel van Vugt 
This bug is not a duplicate of bug 1510570. This bug is caused by the
fix for bug 1510570 :)

** This bug is no longer a duplicate of bug 1510570
   Bluetooth LE pairing fail

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

Title:
  Bluetooth is turned off at boot with latest update (bluez
  5.37-0ubuntu5.2)

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  With latest update, BLUEZ is now off right after boot, as opposed to
  previous behaviour that was on/off depending on last setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 22 16:08:20 2018
  InstallationDate: Installed on 2017-09-29 (115 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04f2:b59d Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76
  dmi.board.version: lemu7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Lemur
  dmi.product.version: lemu7
  dmi.sys.vendor: System76
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: AC:ED:5C:F6:32:44  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:667 acl:0 sco:0 events:38 errors:0
TX bytes:405 acl:0 sco:0 commands:38 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2017-12-06T11:16:58.937870
  mtime.conffile..etc.bluetooth.main.conf: 2018-01-18T18:34:20.102879

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

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

[Kernel-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.

2018-01-23 Thread Daniel van Vugt 
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  Touchpad input doesn't work after longer suspend.

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  When I resume my laptop from a longer (not sure what the threshold is
  yet) suspend, I don't get input from the touchpad, a short suspend
  cycle fixes it.

  Touchscreen works all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:20:56 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718654/+subscriptions

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

[Kernel-packages] [Bug 1729391] Re: Trackpad stops responding after suspend

2018-01-23 Thread Daniel van Vugt 
It's been a while. And Jeppe has already said that 4.13.12 fixes the
issue. Both here and in bug 1718654. Maybe assume 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/1729391

Title:
  Trackpad stops responding after suspend

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

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, the trackpad
  stops working after suspend (it actually works for a few seconds, then
  doesn't react). I can still use the touch screen.

  Please tell me which log-files to upload.

  Thanks

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

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

[Kernel-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work

2018-01-23 Thread Daniel van Vugt 
** Changed in: bluez (Ubuntu)
   Status: Fix Released => 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/123920

Title:
  Bluetooth Logitech Dinovo Keyboard/Mouse don't work

Status in Bluez Utilities:
  New
Status in Bluez-utils:
  New
Status in Linux Mint:
  Invalid
Status in Unity:
  Invalid
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Invalid

Bug description:
  Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will 
work until Nautilus starts.  After Nautilus starts the keyboard and mouse are 
unresponsive and do not work.
  I tried reconnecting the keyboard and mouse by using the discovery buttons on 
both the Bluetooth Dongle and Input device.  The problem still persists.
  Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. 
 Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech 
mini bluetooth receiver.

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

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

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-01-23 Thread Bharata Kalbuaji 
I just upgraded the kernel to 4.13.0-31 but the problem still persists.
I am using Kubuntu 17.10 and after I reboot, I can not start the X
server. If I try to start it, it shows message that it can not find
opengl 2. Any idea how to fix this? I install the nvidia driver via
repository.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-23 Thread Daniel Carosone 
This was the problem that caused me to roll back to Zesty shortly after
Artful was released. I just redid the upgrade because of the EoL,
expecting that it surely would have been fixed in the meantime, but alas
not.

At least this time I could eventually find a bug and workaround :)

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Artful:
  Confirmed

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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

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

2018-01-23 Thread Josep Pujadas-Jubany 
Curiously, if I turn off the system, connect/disconnect the battery
(battery reset hole at the bottom of the laptop) and turn on the system,
NO errors.

At next boot, errors reappear.

https://bugzilla.kernel.org/show_bug.cgi?id=194825#c24

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

** Summary changed:

- Unstable LTS kernel 4.13.0-26
+ Unstable LTS kernel 4.13

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

Title:
  Unstable LTS kernel 4.13

Status in linux-signed package in Ubuntu:
  Confirmed

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

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

  unexpected irq trap at vector

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

  At home (no signed kernel, old machine) my VirtualBox freezes also the
  machine, as explained at
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14

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

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

[Kernel-packages] [Bug 1743094] Re: hibernation broken (freezes with resume) in kernel linux-image-4.13.0-26-generic

2018-01-23 Thread DenisP 
I can confirm that my Laptop freezes on resume from hibernate with Kernel 
4.13.0-25 and 4.13.0-31. Last working Kernel version is 4.13.0-21 .
My Laptop is Lenovo Thinkpad T470.

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

Title:
  hibernation broken (freezes with resume) in kernel linux-
  image-4.13.0-26-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1745054] [NEW] Xenial update to 4.4.108 stable release

2018-01-23 Thread Khaled El Mously 
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.108 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.108 stable release shall be applied:
* arm64: Initialise high_memory global variable earlier
* cxl: Check if vphb exists before iterating over AFU devices
* x86/mm: Add INVPCID helpers
* x86/mm: Fix INVPCID asm constraint
* x86/mm: Add a 'noinvpcid' boot option to turn off INVPCID
* x86/mm: If INVPCID is available, use it to flush global mappings
* mm/rmap: batched invalidations should use existing api
* mm/mmu_context, sched/core: Fix mmu_context.h assumption
* sched/core: Add switch_mm_irqs_off() and use it in the scheduler
* x86/mm: Build arch/x86/mm/tlb.c even on !SMP
* x86/mm, sched/core: Uninline switch_mm()
* x86/mm, sched/core: Turn off IRQs in switch_mm()
* ARM: Hide finish_arch_post_lock_switch() from modules
* sched/core: Idle_task_exit() shouldn't use switch_mm_irqs_off()
* x86/irq: Do not substract irq_tlb_count from irq_call_count
* ALSA: hda - add support for docking station for HP 820 G2
* ALSA: hda - add support for docking station for HP 840 G3
* arm: kprobes: Fix the return address of multiple kretprobes
* arm: kprobes: Align stack to 8-bytes in test code
* cpuidle: Validate cpu_dev in cpuidle_add_sysfs()
* r8152: fix the list rx_done may be used without initialization
* crypto: deadlock between crypto_alg_sem/rtnl_mutex/genl_mutex
* sch_dsmark: fix invalid skb_cow() usage
* bna: integer overflow bug in debugfs
* net: qmi_wwan: Add USB IDs for MDM6600 modem on Motorola Droid 4
* usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed
* usb: gadget: udc: remove pointer dereference after free
* netfilter: nfnl_cthelper: fix runtime expectation policy updates
* netfilter: nfnl_cthelper: Fix memory leak
* inet: frag: release spinlock before calling icmp_send()
* pinctrl: st: add irq_request/release_resources callbacks
* scsi: lpfc: Fix PT2PT PRLI reject
* KVM: x86: correct async page present tracepoint
* KVM: VMX: Fix enable VPID conditions
* ARM: dts: ti: fix PCI bus dtc warnings
* hwmon: (asus_atk0110) fix uninitialized data access
* HID: xinmo: fix for out of range for THT 2P arcade controller.
* r8152: prevent the driver from transmitting packets with carrier off
* s390/qeth: no ETH header for outbound AF_IUCV
* bna: avoid writing uninitialized data into hw registers
* net: Do not allow negative values for busy_read and busy_poll sysctl 
interfaces
* i40e: Do not enable NAPI on q_vectors that have no rings
* RDMA/iser: Fix possible mr leak on device removal event
* irda: vlsi_ir: fix check for DMA mapping errors
* netfilter: nfnl_cthelper: fix a race when walk the nf_ct_helper_hash table
* netfilter: nf_nat_snmp: Fix panic when snmp_trap_helper fails to register
* ARM: dts: am335x-evmsk: adjust mmc2 param to allow suspend
* KVM: pci-assign: do not map smm memory slot pages in vt-d page tables
* isdn: kcapi: avoid uninitialized data
* xhci: plat: Register shutdown for xhci_plat
* netfilter: nfnetlink_queue: fix secctx memory leak
* ARM: dma-mapping: disallow dma_get_sgtable() for non-kernel managed memory
* cpuidle: powernv: Pass correct drv->cpumask for registration
* bnxt_en: Fix NULL pointer dereference in reopen failure path
* backlight: pwm_bl: Fix overflow condition
* crypto: crypto4xx - increase context and scatter ring buffer elements
* rtc: pl031: make interrupt optional
* net: phy: at803x: Change error to EINVAL for invalid MAC
* PCI: Avoid bus reset if bridge itself is broken
* scsi: cxgb4i: fix Tx skb leak
* scsi: mpt3sas: Fix IO error occurs on pulling out a drive from RAID1 volume 
created on two SATA drive
* PCI: Create SR-IOV virtfn/physfn links before attaching driver
* igb: check memory allocation failure
* ixgbe: fix use of uninitialized padding
* PCI/AER: Report non-fatal errors only to the affected endpoint
* scsi: lpfc: Fix secure firmware updates
* scsi: lpfc: PLOGI failures during NPIV testing
* fm10k: ensure we process SM mbx when processing VF mbx
* tcp: fix under-evaluated ssthresh in TCP Vegas
* rtc: set the alarm to the next expiring timer
* cpuidle: fix broadcast control when broadcast can not be entered
* thermal: hisilicon: Handle return value of clk_prepare_enable
* MIPS: math-emu: Fix final emulation phase for certain instructions
* Revert "Bluetooth: btusb: driver to enable the usb-wakeup feature"
* ALSA: hda - Clear the leftover component assignment at snd_hdac_i915_exit()
* ALSA: hda - Degrade i915 binding failure message
* ALSA: hda - Fix yet another i915

[Kernel-packages] [Bug 1745052] Re: Xenial update to 4.4.107 stable release

2018-01-23 Thread Khaled El Mously 
Regarding comment #2: "applied manually" as in using 'patch'

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

Title:
  Xenial update to 4.4.107 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.107 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.107 stable release shall be applied:
  * crypto: hmac - require that the underlying hash algorithm is unkeyed
  * crypto: salsa20 - fix blkcipher_walk API usage
  * autofs: fix careless error in recent commit
  * tracing: Allocate mask_str buffer dynamically
  * USB: uas and storage: Add US_FL_BROKEN_FUA for another JMicron JMS567 ID
  * USB: core: prevent malicious bNumInterfaces overflow
  * usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer
  * ceph: drop negative child dentries before try pruning inode's alias
  * Bluetooth: btusb: driver to enable the usb-wakeup feature
  * xhci: Don't add a virt_dev to the devs array before it's fully allocated
  * sched/rt: Do not pull from current CPU if only one CPU to pull
  * dmaengine: dmatest: move callback wait queue to thread context
  * ext4: fix fdatasync(2) after fallocate(2) operation
  * ext4: fix crash when a directory's i_size is too small
  * KEYS: add missing permission check for request_key() destination
  * mac80211: Fix addition of mesh configuration element
  * usb: phy: isp1301: Add OF device ID table
  * md-cluster: free md_cluster_info if node leave cluster
  * userfaultfd: shmem: __do_fault requires VM_FAULT_NOPAGE
  * userfaultfd: selftest: vm: allow to build in vm/ directory
  * net: initialize msg.msg_flags in recvfrom
  * net: bcmgenet: correct the RBUF_OVFL_CNT and RBUF_ERR_CNT MIB values
  * net: bcmgenet: correct MIB access of UniMAC RUNT counters
  * net: bcmgenet: reserved phy revisions must be checked first
  * net: bcmgenet: power down internal phy if open or resume fails
  * net: bcmgenet: Power up the internal PHY before probing the MII
  * NFSD: fix nfsd_minorversion(.., NFSD_AVAIL)
  * NFSD: fix nfsd_reset_versions for NFSv4.
  * Input: i8042 - add TUXEDO BU1406 (N24_25BU) to the nomux list
  * drm/omap: fix dmabuf mmap for dma_alloc'ed buffers
  * netfilter: bridge: honor frag_max_size when refragmenting
  * writeback: fix memory leak in wb_queue_work()
  * net: wimax/i2400m: fix NULL-deref at probe
  * dmaengine: Fix array index out of bounds warning in __get_unmap_pool()
  * net: Resend IGMP memberships upon peer notification.
  * mlxsw: reg: Fix SPVM max record count
  * mlxsw: reg: Fix SPVMLR max record count
  * intel_th: pci: Add Gemini Lake support
  * openrisc: fix issue handling 8 byte get_user calls
  * scsi: hpsa: update check for logical volume status
  * scsi: hpsa: limit outstanding rescans
  * fjes: Fix wrong netdevice feature flags
  * drm/radeon/si: add dpm quirk for Oland
  * sched/deadline: Make sure the replenishment timer fires in the next period
  * sched/deadline: Throttle a constrained deadline task activated after the 
deadline
  * sched/deadline: Use deadline instead of period when calculating overflow
  * mmc: mediatek: Fixed bug where clock frequency could be set wrong
  * drm/radeon: reinstate oland workaround for sclk
  * afs: Fix missing put_page()
  * afs: Populate group ID from vnode status
  * afs: Adjust mode bits processing
  * afs: Flush outstanding writes when an fd is closed
  * afs: Migrate vlocation fields to 64-bit
  * afs: Prevent callback expiry timer overflow
  * afs: Fix the maths in afs_fs_store_data()
  * afs: Populate and use client modification time
  * afs: Fix page leak in afs_write_begin()
  * afs: Fix afs_kill_pages()
  * net/mlx4_core: Avoid delays during VF driver device shutdown
  * perf symbols: Fix symbols__fixup_end heuristic for corner cases
  * efi/esrt: Cleanup bad memory map log messages
  * NFSv4.1 respect server's max size in CREATE_SESSION
  * btrfs: add missing memset while reading compressed inline extents
  * target: Use system workqueue for ALUA transitions
  * target: fix ALUA transition timeout handling
  * target: fix race during implicit transition work flushes
  * sfc: don't warn on successful change of MAC
  * fbdev: controlfb: Add missing modes to fix out of bounds access
  * video: udlfb: Fix read EDID timeout
  * video: fbdev: au1200fb: Release some resources if a memory allocation fails
  * video: fbdev:

[Kernel-packages] [Bug 1745052] Re: Xenial update to 4.4.107 stable release

2018-01-23 Thread Khaled El Mously 
The following patches were not applied cleanly by 'git am' so I had to
apply them manually. No code changes were required:

 * Bluetooth: btusb: driver to enable the usb-wakeup feature
 * net: initialize msg.msg_flags in recvfrom

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

Title:
  Xenial update to 4.4.107 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.107 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.107 stable release shall be applied:
  * crypto: hmac - require that the underlying hash algorithm is unkeyed
  * crypto: salsa20 - fix blkcipher_walk API usage
  * autofs: fix careless error in recent commit
  * tracing: Allocate mask_str buffer dynamically
  * USB: uas and storage: Add US_FL_BROKEN_FUA for another JMicron JMS567 ID
  * USB: core: prevent malicious bNumInterfaces overflow
  * usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer
  * ceph: drop negative child dentries before try pruning inode's alias
  * Bluetooth: btusb: driver to enable the usb-wakeup feature
  * xhci: Don't add a virt_dev to the devs array before it's fully allocated
  * sched/rt: Do not pull from current CPU if only one CPU to pull
  * dmaengine: dmatest: move callback wait queue to thread context
  * ext4: fix fdatasync(2) after fallocate(2) operation
  * ext4: fix crash when a directory's i_size is too small
  * KEYS: add missing permission check for request_key() destination
  * mac80211: Fix addition of mesh configuration element
  * usb: phy: isp1301: Add OF device ID table
  * md-cluster: free md_cluster_info if node leave cluster
  * userfaultfd: shmem: __do_fault requires VM_FAULT_NOPAGE
  * userfaultfd: selftest: vm: allow to build in vm/ directory
  * net: initialize msg.msg_flags in recvfrom
  * net: bcmgenet: correct the RBUF_OVFL_CNT and RBUF_ERR_CNT MIB values
  * net: bcmgenet: correct MIB access of UniMAC RUNT counters
  * net: bcmgenet: reserved phy revisions must be checked first
  * net: bcmgenet: power down internal phy if open or resume fails
  * net: bcmgenet: Power up the internal PHY before probing the MII
  * NFSD: fix nfsd_minorversion(.., NFSD_AVAIL)
  * NFSD: fix nfsd_reset_versions for NFSv4.
  * Input: i8042 - add TUXEDO BU1406 (N24_25BU) to the nomux list
  * drm/omap: fix dmabuf mmap for dma_alloc'ed buffers
  * netfilter: bridge: honor frag_max_size when refragmenting
  * writeback: fix memory leak in wb_queue_work()
  * net: wimax/i2400m: fix NULL-deref at probe
  * dmaengine: Fix array index out of bounds warning in __get_unmap_pool()
  * net: Resend IGMP memberships upon peer notification.
  * mlxsw: reg: Fix SPVM max record count
  * mlxsw: reg: Fix SPVMLR max record count
  * intel_th: pci: Add Gemini Lake support
  * openrisc: fix issue handling 8 byte get_user calls
  * scsi: hpsa: update check for logical volume status
  * scsi: hpsa: limit outstanding rescans
  * fjes: Fix wrong netdevice feature flags
  * drm/radeon/si: add dpm quirk for Oland
  * sched/deadline: Make sure the replenishment timer fires in the next period
  * sched/deadline: Throttle a constrained deadline task activated after the 
deadline
  * sched/deadline: Use deadline instead of period when calculating overflow
  * mmc: mediatek: Fixed bug where clock frequency could be set wrong
  * drm/radeon: reinstate oland workaround for sclk
  * afs: Fix missing put_page()
  * afs: Populate group ID from vnode status
  * afs: Adjust mode bits processing
  * afs: Flush outstanding writes when an fd is closed
  * afs: Migrate vlocation fields to 64-bit
  * afs: Prevent callback expiry timer overflow
  * afs: Fix the maths in afs_fs_store_data()
  * afs: Populate and use client modification time
  * afs: Fix page leak in afs_write_begin()
  * afs: Fix afs_kill_pages()
  * net/mlx4_core: Avoid delays during VF driver device shutdown
  * perf symbols: Fix symbols__fixup_end heuristic for corner cases
  * efi/esrt: Cleanup bad memory map log messages
  * NFSv4.1 respect server's max size in CREATE_SESSION
  * btrfs: add missing memset while reading compressed inline extents
  * target: Use system workqueue for ALUA transitions
  * target: fix ALUA transition timeout handling
  * target: fix race during implicit transition work flushes
  * sfc: don't warn on successful change of MAC
  * fbdev: controlfb: Add missing modes

[Kernel-packages] [Bug 1745052] Re: Xenial update to 4.4.107 stable release

2018-01-23 Thread Khaled El Mously 
The following patch was NOT applied because it was already applied in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672785

 * net/mlx4_core: Avoid delays during VF driver device shutdown

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

Title:
  Xenial update to 4.4.107 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.107 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.107 stable release shall be applied:
  * crypto: hmac - require that the underlying hash algorithm is unkeyed
  * crypto: salsa20 - fix blkcipher_walk API usage
  * autofs: fix careless error in recent commit
  * tracing: Allocate mask_str buffer dynamically
  * USB: uas and storage: Add US_FL_BROKEN_FUA for another JMicron JMS567 ID
  * USB: core: prevent malicious bNumInterfaces overflow
  * usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer
  * ceph: drop negative child dentries before try pruning inode's alias
  * Bluetooth: btusb: driver to enable the usb-wakeup feature
  * xhci: Don't add a virt_dev to the devs array before it's fully allocated
  * sched/rt: Do not pull from current CPU if only one CPU to pull
  * dmaengine: dmatest: move callback wait queue to thread context
  * ext4: fix fdatasync(2) after fallocate(2) operation
  * ext4: fix crash when a directory's i_size is too small
  * KEYS: add missing permission check for request_key() destination
  * mac80211: Fix addition of mesh configuration element
  * usb: phy: isp1301: Add OF device ID table
  * md-cluster: free md_cluster_info if node leave cluster
  * userfaultfd: shmem: __do_fault requires VM_FAULT_NOPAGE
  * userfaultfd: selftest: vm: allow to build in vm/ directory
  * net: initialize msg.msg_flags in recvfrom
  * net: bcmgenet: correct the RBUF_OVFL_CNT and RBUF_ERR_CNT MIB values
  * net: bcmgenet: correct MIB access of UniMAC RUNT counters
  * net: bcmgenet: reserved phy revisions must be checked first
  * net: bcmgenet: power down internal phy if open or resume fails
  * net: bcmgenet: Power up the internal PHY before probing the MII
  * NFSD: fix nfsd_minorversion(.., NFSD_AVAIL)
  * NFSD: fix nfsd_reset_versions for NFSv4.
  * Input: i8042 - add TUXEDO BU1406 (N24_25BU) to the nomux list
  * drm/omap: fix dmabuf mmap for dma_alloc'ed buffers
  * netfilter: bridge: honor frag_max_size when refragmenting
  * writeback: fix memory leak in wb_queue_work()
  * net: wimax/i2400m: fix NULL-deref at probe
  * dmaengine: Fix array index out of bounds warning in __get_unmap_pool()
  * net: Resend IGMP memberships upon peer notification.
  * mlxsw: reg: Fix SPVM max record count
  * mlxsw: reg: Fix SPVMLR max record count
  * intel_th: pci: Add Gemini Lake support
  * openrisc: fix issue handling 8 byte get_user calls
  * scsi: hpsa: update check for logical volume status
  * scsi: hpsa: limit outstanding rescans
  * fjes: Fix wrong netdevice feature flags
  * drm/radeon/si: add dpm quirk for Oland
  * sched/deadline: Make sure the replenishment timer fires in the next period
  * sched/deadline: Throttle a constrained deadline task activated after the 
deadline
  * sched/deadline: Use deadline instead of period when calculating overflow
  * mmc: mediatek: Fixed bug where clock frequency could be set wrong
  * drm/radeon: reinstate oland workaround for sclk
  * afs: Fix missing put_page()
  * afs: Populate group ID from vnode status
  * afs: Adjust mode bits processing
  * afs: Flush outstanding writes when an fd is closed
  * afs: Migrate vlocation fields to 64-bit
  * afs: Prevent callback expiry timer overflow
  * afs: Fix the maths in afs_fs_store_data()
  * afs: Populate and use client modification time
  * afs: Fix page leak in afs_write_begin()
  * afs: Fix afs_kill_pages()
  * net/mlx4_core: Avoid delays during VF driver device shutdown
  * perf symbols: Fix symbols__fixup_end heuristic for corner cases
  * efi/esrt: Cleanup bad memory map log messages
  * NFSv4.1 respect server's max size in CREATE_SESSION
  * btrfs: add missing memset while reading compressed inline extents
  * target: Use system workqueue for ALUA transitions
  * target: fix ALUA transition timeout handling
  * target: fix race during implicit transition work flushes
  * sfc: don't warn on successful change of MAC
  * fbdev: controlfb: Add missing modes to fix out of bounds access
  *

[Kernel-packages] [Bug 1745052] Re: Xenial update to 4.4.107 stable release

2018-01-23 Thread Khaled El Mously 
** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.107 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.107 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.107 stable release shall be
- applied:
+    The following patches from the 4.4.107 stable release shall be applied:
+ * crypto: hmac - require that the underlying hash algorithm is unkeyed
+ * crypto: salsa20 - fix blkcipher_walk API usage
+ * autofs: fix careless error in recent commit
+ * tracing: Allocate mask_str buffer dynamically
+ * USB: uas and storage: Add US_FL_BROKEN_FUA for another JMicron JMS567 ID
+ * USB: core: prevent malicious bNumInterfaces overflow
+ * usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer
+ * ceph: drop negative child dentries before try pruning inode's alias
+ * Bluetooth: btusb: driver to enable the usb-wakeup feature
+ * xhci: Don't add a virt_dev to the devs array before it's fully allocated
+ * sched/rt: Do not pull from current CPU if only one CPU to pull
+ * dmaengine: dmatest: move callback wait queue to thread context
+ * ext4: fix fdatasync(2) after fallocate(2) operation
+ * ext4: fix crash when a directory's i_size is too small
+ * KEYS: add missing permission check for request_key() destination
+ * mac80211: Fix addition of mesh configuration element
+ * usb: phy: isp1301: Add OF device ID table
+ * md-cluster: free md_cluster_info if node leave cluster
+ * userfaultfd: shmem: __do_fault requires VM_FAULT_NOPAGE
+ * userfaultfd: selftest: vm: allow to build in vm/ directory
+ * net: initialize msg.msg_flags in recvfrom
+ * net: bcmgenet: correct the RBUF_OVFL_CNT and RBUF_ERR_CNT MIB values
+ * net: bcmgenet: correct MIB access of UniMAC RUNT counters
+ * net: bcmgenet: reserved phy revisions must be checked first
+ * net: bcmgenet: power down internal phy if open or resume fails
+ * net: bcmgenet: Power up the internal PHY before probing the MII
+ * NFSD: fix nfsd_minorversion(.., NFSD_AVAIL)
+ * NFSD: fix nfsd_reset_versions for NFSv4.
+ * Input: i8042 - add TUXEDO BU1406 (N24_25BU) to the nomux list
+ * drm/omap: fix dmabuf mmap for dma_alloc'ed buffers
+ * netfilter: bridge: honor frag_max_size when refragmenting
+ * writeback: fix memory leak in wb_queue_work()
+ * net: wimax/i2400m: fix NULL-deref at probe
+ * dmaengine: Fix array index out of bounds warning in __get_unmap_pool()
+ * net: Resend IGMP memberships upon peer notification.
+ * mlxsw: reg: Fix SPVM max record count
+ * mlxsw: reg: Fix SPVMLR max record count
+ * intel_th: pci: Add Gemini Lake support
+ * openrisc: fix issue handling 8 byte get_user calls
+ * scsi: hpsa: update check for logical volume status
+ * scsi: hpsa: limit outstanding rescans
+ * fjes: Fix wrong netdevice feature flags
+ * drm/radeon/si: add dpm quirk for Oland
+ * sched/deadline: Make sure the replenishment timer fires in the next period
+ * sched/deadline: Throttle a constrained deadline task activated after the 
deadline
+ * sched/deadline: Use deadline instead of period when calculating overflow
+ * mmc: mediatek: Fixed bug where clock frequency could be set wrong
+ * drm/radeon: reinstate oland workaround for sclk
+ * afs: Fix missing put_page()
+ * afs: Populate group ID from vnode status
+ * afs: Adjust mode bits processing
+ * afs: Flush outstanding writes when an fd is closed
+ * afs: Migrate vlocation fields to 64-bit
+ * afs: Prevent callback expiry timer overflow
+ * afs: Fix the maths in afs_fs_store_data()
+ * afs: Populate and use client modification time
+ * afs: Fix page leak in afs_write_begin()
+ * afs: Fix afs_kill_pages()
+ * net/mlx4_core: Avoid delays during VF driver device shutdown
+ * perf symbols: Fix symbols__fixup_end heuristic for corner cases
+ * efi/esrt: Cleanup bad memory map log messages
+ * NFSv4.1 respect server's max size in CREATE_SESSION
+ * btrfs: add missing memset while reading compressed inline extents
+ * target: Use system workqueue for ALUA transitions
+ * target: fix ALUA

[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working

2018-01-23 Thread TauSo 
I've tried some of the mainline kernels and finally got to this situation:
last working kernel: v4.11.12 mainline build [1]
first non working kernel: v4.12-rc1 mainline build [2]

Hope that will help to find the bug.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11.12/
[2] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/

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

Title:
  DVB Card with SAA7146 chipset not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card
  Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore.
  There is a kernel bug message while booting and no /dev/dvb device is
  created. Tried also with newest mainline 4.14 kernel - same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-25-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Wed Jan 10 00:42:24 2018
  HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456
  InstallationDate: Installed on 2016-02-13 (696 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 
(20151021)
  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.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force 
video=LVDS-1:d vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago)
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: AD2700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX: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/1742316/+subscriptions

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

[Kernel-packages] [Bug 1745047] Re: Xenial update to 4.4.106 stable release

2018-01-23 Thread Khaled El Mously 
The following patches were NOT applied as they were already applied:

 * scsi: storvsc: Workaround for virtual DVD SCSI version
 * more bio_map_user_iov() leak fixes

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

Title:
  Xenial update to 4.4.106 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.106 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.106 stable release shall be applied:
  * can: ti_hecc: Fix napi poll return value for repoll
  * can: kvaser_usb: free buf in error paths
  * can: kvaser_usb: Fix comparison bug in kvaser_usb_read_bulk_callback()
  * can: kvaser_usb: ratelimit errors if incomplete messages are received
  * can: kvaser_usb: cancel urb on -EPIPE and -EPROTO
  * can: ems_usb: cancel urb on -EPIPE and -EPROTO
  * can: esd_usb2: cancel urb on -EPIPE and -EPROTO
  * can: usb_8dev: cancel urb on -EPIPE and -EPROTO
  * virtio: release virtio index when fail to device_register
  * hv: kvp: Avoid reading past allocated blocks from KVP file
  * isa: Prevent NULL dereference in isa_bus driver callbacks
  * scsi: libsas: align sata_device's rps_resp on a cacheline
  * efi: Move some sysfs files to be read-only by root
  * ASN.1: fix out-of-bounds read when parsing indefinite length item
  * ASN.1: check for error from ASN1_OP_END__ACT actions
  * X.509: reject invalid BIT STRING for subjectPublicKey
  * x86/PCI: Make broadcom_postcore_init() check acpi_disabled
  * ALSA: pcm: prevent UAF in snd_pcm_info
  * ALSA: seq: Remove spurious WARN_ON() at timer check
  * ALSA: usb-audio: Fix out-of-bound error
  * ALSA: usb-audio: Add check return value for usb_string()
  * iommu/vt-d: Fix scatterlist offset handling
  * s390: fix compat system call table
  * kdb: Fix handling of kallsyms_symbol_next() return value
  * drm: extra printk() wrapper macros
  * drm/exynos: gem: Drop NONCONTIG flag for buffers allocated without IOMMU
  * media: dvb: i2c transfers over usb cannot be done from stack
  * arm64: KVM: fix VTTBR_BADDR_MASK BUG_ON off-by-one
  * KVM: VMX: remove I/O port 0x80 bypass on Intel hosts
  * arm64: fpsimd: Prevent registers leaking from dead tasks
  * ARM: BUG if jumping to usermode address in kernel mode
  * ARM: avoid faulting on qemu
  * scsi: storvsc: Workaround for virtual DVD SCSI version
  * thp: reduce indentation level in change_huge_pmd()
  * thp: fix MADV_DONTNEED vs. numa balancing race
  * mm: drop unused pmdp_huge_get_and_clear_notify()
  * Revert "drm/armada: Fix compile fail"
  * Revert "spi: SPI_FSL_DSPI should depend on HAS_DMA"
  * Revert "s390/kbuild: enable modversions for symbols exported from asm"
  * vti6: Don't report path MTU below IPV6_MIN_MTU.
  * ARM: OMAP2+: gpmc-onenand: propagate error on initialization failure
  * x86/hpet: Prevent might sleep splat on resume
  * selftest/powerpc: Fix false failures for skipped tests
  * module: set __jump_table alignment to 8
  * ARM: OMAP2+: Fix device node reference counts
  * ARM: OMAP2+: Release device node after it is no longer needed.
  * gpio: altera: Use handle_level_irq when configured as a level_high
  * HID: chicony: Add support for another ASUS Zen AiO keyboard
  * usb: gadget: configs: plug memory leak
  * USB: gadgetfs: Fix a potential memory leak in 'dev_config()'
  * kvm: nVMX: VMCLEAR should not cause the vCPU to shut down
  * libata: drop WARN from protocol error in ata_sff_qc_issue()
  * workqueue: trigger WARN if queue_delayed_work() is called with NULL @wq
  * scsi: lpfc: Fix crash during Hardware error recovery on SLI3 adapters
  * irqchip/crossbar: Fix incorrect type of register size
  * KVM: nVMX: reset nested_run_pending if the vCPU is going to be reset
  * arm: KVM: Survive unknown traps from guests
  * arm64: KVM: Survive unknown traps from guests
  * spi_ks8995: fix "BUG: key accdaa28 not in .data!"
  * bnx2x: prevent crash when accessing PTP with interface down
  * bnx2x: fix possible overrun of VFPF multicast addresses array
  * bnx2x: do not rollback VF MAC/VLAN filters we did not configure
  * ipv6: reorder icmpv6_init() and ip6_mr_init()
  * crypto: s5p-sss - Fix completing crypto request in IRQ handler
  * i2c: riic: fix restart condition
  * zram: set physical queue limits to avoid array out of bounds accesses
  * netfilter: don't track fragmented packets
  * axonram: Fix gendisk handling
  * drm/amd/amdgpu:

[Kernel-packages] [Bug 1745052] [NEW] Xenial update to 4.4.107 stable release

2018-01-23 Thread Khaled El Mously 
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.107 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.107 stable release shall be applied:
* crypto: hmac - require that the underlying hash algorithm is unkeyed
* crypto: salsa20 - fix blkcipher_walk API usage
* autofs: fix careless error in recent commit
* tracing: Allocate mask_str buffer dynamically
* USB: uas and storage: Add US_FL_BROKEN_FUA for another JMicron JMS567 ID
* USB: core: prevent malicious bNumInterfaces overflow
* usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer
* ceph: drop negative child dentries before try pruning inode's alias
* Bluetooth: btusb: driver to enable the usb-wakeup feature
* xhci: Don't add a virt_dev to the devs array before it's fully allocated
* sched/rt: Do not pull from current CPU if only one CPU to pull
* dmaengine: dmatest: move callback wait queue to thread context
* ext4: fix fdatasync(2) after fallocate(2) operation
* ext4: fix crash when a directory's i_size is too small
* KEYS: add missing permission check for request_key() destination
* mac80211: Fix addition of mesh configuration element
* usb: phy: isp1301: Add OF device ID table
* md-cluster: free md_cluster_info if node leave cluster
* userfaultfd: shmem: __do_fault requires VM_FAULT_NOPAGE
* userfaultfd: selftest: vm: allow to build in vm/ directory
* net: initialize msg.msg_flags in recvfrom
* net: bcmgenet: correct the RBUF_OVFL_CNT and RBUF_ERR_CNT MIB values
* net: bcmgenet: correct MIB access of UniMAC RUNT counters
* net: bcmgenet: reserved phy revisions must be checked first
* net: bcmgenet: power down internal phy if open or resume fails
* net: bcmgenet: Power up the internal PHY before probing the MII
* NFSD: fix nfsd_minorversion(.., NFSD_AVAIL)
* NFSD: fix nfsd_reset_versions for NFSv4.
* Input: i8042 - add TUXEDO BU1406 (N24_25BU) to the nomux list
* drm/omap: fix dmabuf mmap for dma_alloc'ed buffers
* netfilter: bridge: honor frag_max_size when refragmenting
* writeback: fix memory leak in wb_queue_work()
* net: wimax/i2400m: fix NULL-deref at probe
* dmaengine: Fix array index out of bounds warning in __get_unmap_pool()
* net: Resend IGMP memberships upon peer notification.
* mlxsw: reg: Fix SPVM max record count
* mlxsw: reg: Fix SPVMLR max record count
* intel_th: pci: Add Gemini Lake support
* openrisc: fix issue handling 8 byte get_user calls
* scsi: hpsa: update check for logical volume status
* scsi: hpsa: limit outstanding rescans
* fjes: Fix wrong netdevice feature flags
* drm/radeon/si: add dpm quirk for Oland
* sched/deadline: Make sure the replenishment timer fires in the next period
* sched/deadline: Throttle a constrained deadline task activated after the 
deadline
* sched/deadline: Use deadline instead of period when calculating overflow
* mmc: mediatek: Fixed bug where clock frequency could be set wrong
* drm/radeon: reinstate oland workaround for sclk
* afs: Fix missing put_page()
* afs: Populate group ID from vnode status
* afs: Adjust mode bits processing
* afs: Flush outstanding writes when an fd is closed
* afs: Migrate vlocation fields to 64-bit
* afs: Prevent callback expiry timer overflow
* afs: Fix the maths in afs_fs_store_data()
* afs: Populate and use client modification time
* afs: Fix page leak in afs_write_begin()
* afs: Fix afs_kill_pages()
* net/mlx4_core: Avoid delays during VF driver device shutdown
* perf symbols: Fix symbols__fixup_end heuristic for corner cases
* efi/esrt: Cleanup bad memory map log messages
* NFSv4.1 respect server's max size in CREATE_SESSION
* btrfs: add missing memset while reading compressed inline extents
* target: Use system workqueue for ALUA transitions
* target: fix ALUA transition timeout handling
* target: fix race during implicit transition work flushes
* sfc: don't warn on successful change of MAC
* fbdev: controlfb: Add missing modes to fix out of bounds access
* video: udlfb: Fix read EDID timeout
* video: fbdev: au1200fb: Release some resources if a memory allocation fails
* video: fbdev: au1200fb: Return an error code if a memory allocation fails
* rtc: pcf8563: fix output clock rate
* dmaengine: ti-dma-crossbar: Correct am335x/am43xx mux value type
* PCI/PME: Handle invalid data when reading Root Status
* powerpc/powernv/cpufreq: Fix the frequency read by /proc/cpuinfo
* netfilter: ipvs: Fix inappropriate output of procfs
* powerpc/opal: Fix EBUSY bug in acquiring tokens
* powerpc/ipic: Fix status get and status clear
* target/iscsi: Fix a race condition in

[Kernel-packages] [Bug 1745046] Re: Xenial update to 4.4.105 stable release

2018-01-23 Thread Khaled El Mously 
The following patch was NOT applied since it was already applied in
http://bugs.launchpad.net/bugs/1519623

 * usb: Add USB 3.1 Precision time measurement capability descriptor
support

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

Title:
  Xenial update to 4.4.105 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.105 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.105 stable release shall be applied:
  * bcache: only permit to recovery read error when cache device is clean
  * bcache: recover data from backing when data is clean
  * uas: Always apply US_FL_NO_ATA_1X quirk to Seagate devices
  * usb: quirks: Add no-lpm quirk for KY-688 USB 3.1 Type-C Hub
  * serial: 8250_pci: Add Amazon PCI serial device ID
  * s390/runtime instrumentation: simplify task exit handling
  * USB: serial: option: add Quectel BG96 id
  * ima: fix hash algorithm initialization
  * s390/pci: do not require AIS facility
  * selftests/x86/ldt_get: Add a few additional tests for limits
  * serial: 8250_fintek: Fix rs485 disablement on invalid ioctl()
  * spi: sh-msiof: Fix DMA transfer size check
  * usb: phy: tahvo: fix error handling in tahvo_usb_probe()
  * serial: 8250: Preserve DLD[7:4] for PORT_XR17V35X
  * x86/entry: Use SYSCALL_DEFINE() macros for sys_modify_ldt()
  * EDAC, sb_edac: Fix missing break in switch
  * sysrq : fix Show Regs call trace on ARM
  * perf test attr: Fix ignored test case result
  * kprobes/x86: Disable preemption in ftrace-based jprobes
  * net: systemport: Utilize skb_put_padto()
  * net: systemport: Pad packet before inserting TSB
  * ARM: OMAP1: DMA: Correct the number of logical channels
  * vti6: fix device register to report IFLA_INFO_KIND
  * net/appletalk: Fix kernel memory disclosure
  * ravb: Remove Rx overflow log messages
  * nfs: Don't take a reference on fl->fl_file for LOCK operation
  * KVM: arm/arm64: Fix occasional warning from the timer work function
  * NFSv4: Fix client recovery when server reboots multiple times
  * drm/exynos/decon5433: set STANDALONE_UPDATE_F on output enablement
  * net: sctp: fix array overrun read on sctp_timer_tbl
  * tipc: fix cleanup at module unload
  * dmaengine: pl330: fix double lock
  * tcp: correct memory barrier usage in tcp_check_space()
  * mm: avoid returning VM_FAULT_RETRY from ->page_mkwrite handlers
  * xen-netfront: Improve error handling during initialization
  * net: fec: fix multicast filtering hardware setup
  * Revert "ocfs2: should wait dio before inode lock in ocfs2_setattr()"
  * usb: hub: Cycle HUB power when initialization fails
  * usb: xhci: fix panic in xhci_free_virt_devices_depth_first
  * usb: Add USB 3.1 Precision time measurement capability descriptor support
  * usb: ch9: Add size macro for SSP dev cap descriptor
  * USB: core: Add type-specific length check of BOS descriptors
  * USB: Increase usbfs transfer limit
  * USB: devio: Prevent integer overflow in proc_do_submiturb()
  * USB: usbfs: Filter flags passed in from user space
  * usb: host: fix incorrect updating of offset
  * xen-netfront: avoid crashing on resume after a failure in talk_to_netback()
  * Linux 4.4.105

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

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

[Kernel-packages] [Bug 1745047] [NEW] Xenial update to 4.4.106 stable release

2018-01-23 Thread Khaled El Mously 
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.106 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.106 stable release shall be applied:
* can: ti_hecc: Fix napi poll return value for repoll
* can: kvaser_usb: free buf in error paths
* can: kvaser_usb: Fix comparison bug in kvaser_usb_read_bulk_callback()
* can: kvaser_usb: ratelimit errors if incomplete messages are received
* can: kvaser_usb: cancel urb on -EPIPE and -EPROTO
* can: ems_usb: cancel urb on -EPIPE and -EPROTO
* can: esd_usb2: cancel urb on -EPIPE and -EPROTO
* can: usb_8dev: cancel urb on -EPIPE and -EPROTO
* virtio: release virtio index when fail to device_register
* hv: kvp: Avoid reading past allocated blocks from KVP file
* isa: Prevent NULL dereference in isa_bus driver callbacks
* scsi: libsas: align sata_device's rps_resp on a cacheline
* efi: Move some sysfs files to be read-only by root
* ASN.1: fix out-of-bounds read when parsing indefinite length item
* ASN.1: check for error from ASN1_OP_END__ACT actions
* X.509: reject invalid BIT STRING for subjectPublicKey
* x86/PCI: Make broadcom_postcore_init() check acpi_disabled
* ALSA: pcm: prevent UAF in snd_pcm_info
* ALSA: seq: Remove spurious WARN_ON() at timer check
* ALSA: usb-audio: Fix out-of-bound error
* ALSA: usb-audio: Add check return value for usb_string()
* iommu/vt-d: Fix scatterlist offset handling
* s390: fix compat system call table
* kdb: Fix handling of kallsyms_symbol_next() return value
* drm: extra printk() wrapper macros
* drm/exynos: gem: Drop NONCONTIG flag for buffers allocated without IOMMU
* media: dvb: i2c transfers over usb cannot be done from stack
* arm64: KVM: fix VTTBR_BADDR_MASK BUG_ON off-by-one
* KVM: VMX: remove I/O port 0x80 bypass on Intel hosts
* arm64: fpsimd: Prevent registers leaking from dead tasks
* ARM: BUG if jumping to usermode address in kernel mode
* ARM: avoid faulting on qemu
* scsi: storvsc: Workaround for virtual DVD SCSI version
* thp: reduce indentation level in change_huge_pmd()
* thp: fix MADV_DONTNEED vs. numa balancing race
* mm: drop unused pmdp_huge_get_and_clear_notify()
* Revert "drm/armada: Fix compile fail"
* Revert "spi: SPI_FSL_DSPI should depend on HAS_DMA"
* Revert "s390/kbuild: enable modversions for symbols exported from asm"
* vti6: Don't report path MTU below IPV6_MIN_MTU.
* ARM: OMAP2+: gpmc-onenand: propagate error on initialization failure
* x86/hpet: Prevent might sleep splat on resume
* selftest/powerpc: Fix false failures for skipped tests
* module: set __jump_table alignment to 8
* ARM: OMAP2+: Fix device node reference counts
* ARM: OMAP2+: Release device node after it is no longer needed.
* gpio: altera: Use handle_level_irq when configured as a level_high
* HID: chicony: Add support for another ASUS Zen AiO keyboard
* usb: gadget: configs: plug memory leak
* USB: gadgetfs: Fix a potential memory leak in 'dev_config()'
* kvm: nVMX: VMCLEAR should not cause the vCPU to shut down
* libata: drop WARN from protocol error in ata_sff_qc_issue()
* workqueue: trigger WARN if queue_delayed_work() is called with NULL @wq
* scsi: lpfc: Fix crash during Hardware error recovery on SLI3 adapters
* irqchip/crossbar: Fix incorrect type of register size
* KVM: nVMX: reset nested_run_pending if the vCPU is going to be reset
* arm: KVM: Survive unknown traps from guests
* arm64: KVM: Survive unknown traps from guests
* spi_ks8995: fix "BUG: key accdaa28 not in .data!"
* bnx2x: prevent crash when accessing PTP with interface down
* bnx2x: fix possible overrun of VFPF multicast addresses array
* bnx2x: do not rollback VF MAC/VLAN filters we did not configure
* ipv6: reorder icmpv6_init() and ip6_mr_init()
* crypto: s5p-sss - Fix completing crypto request in IRQ handler
* i2c: riic: fix restart condition
* zram: set physical queue limits to avoid array out of bounds accesses
* netfilter: don't track fragmented packets
* axonram: Fix gendisk handling
* drm/amd/amdgpu: fix console deadlock if late init failed
* powerpc/powernv/ioda2: Gracefully fail if too many TCE levels requested
* EDAC, i5000, i5400: Fix use of MTR_DRAM_WIDTH macro
* EDAC, i5000, i5400: Fix definition of NRECMEMB register
* kbuild: pkg: use --transform option to prefix paths in tar
* mac80211_hwsim: Fix memory leak in hwsim_new_radio_nl()
* route: also update fnhe_genid when updating a route cache
* route: update fnhe_expires for redirect when the fnhe exists
* lib/genalloc.c: make the avail variable an atomic_long_t
* dynamic-debug-howto: fix optional/omitted ending

[Kernel-packages] [Bug 1745046] [NEW] Xenial update to 4.4.105 stable release

2018-01-23 Thread Khaled El Mously 
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.105 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.105 stable release shall be applied:
* bcache: only permit to recovery read error when cache device is clean
* bcache: recover data from backing when data is clean
* uas: Always apply US_FL_NO_ATA_1X quirk to Seagate devices
* usb: quirks: Add no-lpm quirk for KY-688 USB 3.1 Type-C Hub
* serial: 8250_pci: Add Amazon PCI serial device ID
* s390/runtime instrumentation: simplify task exit handling
* USB: serial: option: add Quectel BG96 id
* ima: fix hash algorithm initialization
* s390/pci: do not require AIS facility
* selftests/x86/ldt_get: Add a few additional tests for limits
* serial: 8250_fintek: Fix rs485 disablement on invalid ioctl()
* spi: sh-msiof: Fix DMA transfer size check
* usb: phy: tahvo: fix error handling in tahvo_usb_probe()
* serial: 8250: Preserve DLD[7:4] for PORT_XR17V35X
* x86/entry: Use SYSCALL_DEFINE() macros for sys_modify_ldt()
* EDAC, sb_edac: Fix missing break in switch
* sysrq : fix Show Regs call trace on ARM
* perf test attr: Fix ignored test case result
* kprobes/x86: Disable preemption in ftrace-based jprobes
* net: systemport: Utilize skb_put_padto()
* net: systemport: Pad packet before inserting TSB
* ARM: OMAP1: DMA: Correct the number of logical channels
* vti6: fix device register to report IFLA_INFO_KIND
* net/appletalk: Fix kernel memory disclosure
* ravb: Remove Rx overflow log messages
* nfs: Don't take a reference on fl->fl_file for LOCK operation
* KVM: arm/arm64: Fix occasional warning from the timer work function
* NFSv4: Fix client recovery when server reboots multiple times
* drm/exynos/decon5433: set STANDALONE_UPDATE_F on output enablement
* net: sctp: fix array overrun read on sctp_timer_tbl
* tipc: fix cleanup at module unload
* dmaengine: pl330: fix double lock
* tcp: correct memory barrier usage in tcp_check_space()
* mm: avoid returning VM_FAULT_RETRY from ->page_mkwrite handlers
* xen-netfront: Improve error handling during initialization
* net: fec: fix multicast filtering hardware setup
* Revert "ocfs2: should wait dio before inode lock in ocfs2_setattr()"
* usb: hub: Cycle HUB power when initialization fails
* usb: xhci: fix panic in xhci_free_virt_devices_depth_first
* usb: Add USB 3.1 Precision time measurement capability descriptor support
* usb: ch9: Add size macro for SSP dev cap descriptor
* USB: core: Add type-specific length check of BOS descriptors
* USB: Increase usbfs transfer limit
* USB: devio: Prevent integer overflow in proc_do_submiturb()
* USB: usbfs: Filter flags passed in from user space
* usb: host: fix incorrect updating of offset
* xen-netfront: avoid crashing on resume after a failure in talk_to_netback()
* Linux 4.4.105

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.105 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.105 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.105 stable release shall be
- applied:
+    The following patches from the 4.4.105 stable release shall be applied:
+ * bcache: only permit to recovery read error when cache device is clean
+ * bcache: recover data from backing when data is clean
+ * uas: Always apply US_FL_NO_ATA_1X quirk to Seagate devices
+ * usb: quirks: Add no-lpm quirk for KY-688 USB 3.1 Type-C Hub
+ * serial: 8250_pci:

[Kernel-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work

2018-01-23 Thread Vadim Fedosov 
Confirm. I have updated 17.04 -> 17.10 and this bug is still exist. Have
to edit hid2hci.rules file as Daniel Beauyat suggest to get it work.
Have this bug since I start using ubuntu 10.04.

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

Title:
  Bluetooth Logitech Dinovo Keyboard/Mouse don't work

Status in Bluez Utilities:
  New
Status in Bluez-utils:
  New
Status in Linux Mint:
  Invalid
Status in Unity:
  Invalid
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Invalid

Bug description:
  Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will 
work until Nautilus starts.  After Nautilus starts the keyboard and mouse are 
unresponsive and do not work.
  I tried reconnecting the keyboard and mouse by using the discovery buttons on 
both the Bluetooth Dongle and Input device.  The problem still persists.
  Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. 
 Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech 
mini bluetooth receiver.

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

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

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

2018-01-23 Thread Ubuntu Kernel Bot 
This change was made by a bot.

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Re: [Kernel-packages] [Bug 1744853] Re: 17.10.1 Cannot boot USB or CDROM or enter Bios

2018-01-23 Thread Lars Pedersen 
*** This bug is a duplicate of bug 1734147 ***
https://bugs.launchpad.net/bugs/1734147

Fair enough. I opened it because it was suggested that it was a new 
issue. Feel free to close it.


On 24/01/2018 7:27 AM, Joseph Salisbury wrote:
> *** This bug is a duplicate of bug 1734147 ***
>  https://bugs.launchpad.net/bugs/1734147
>
> ** This bug has been marked a duplicate of bug 1734147
> corrupted BIOS due to Intel SPI bug in kernel
>

-- 
Cheers
Lars

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

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

Title:
  17.10.1 Cannot boot USB or CDROM or enter Bios

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ACER V5-571G-53314G75Makk, SSID:23302770966

  Installed Ubuntu 17.10.1 yesterday and can longer boot into USB or
  CDROM. Cannot access BIOS(Phoenix) via F2.

  Ubuntu boots fine and works.

  I have followed the steps above in #1734147, installing both kernel
  versions and the BIOS has NOT recovered. I still cannot enter BIOS on
  this machine.

  Any assistance would be greatly appreciated.

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

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

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

2018-01-23 Thread Tomasz Przybysz 
I'm currently at kernel version 4.14.11 and the intel firmware drivers 
installed from
https://01.org/linuxgraphics/downloads/firmware
which are:
kbl_guc_ver9_14.bin
bxt_guc_ver8_7.bin
kbl_dmc_ver1_01.bin

And the bug is still there. Although it wasn't manifesting itself until
I've connected an external screen (may coincidence though).

@Angelo Lisco
Not sure will it help in your case but have you tried setting kernel boot flag?
i915.enable_rc6=0

It's workaround not a fix, I'm afraid.

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go

[Kernel-packages] [Bug 1744979] Re: grub_efi_secure_boot signal at the beginning of the boot process

2018-01-23 Thread Joseph Salisbury 
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-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.4.113

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

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

** Tags added: needs-bisect

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1744995] Re: Spectre kernel update crashes hard

2018-01-23 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags added: kernel-da-key pti

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

Title:
  Spectre kernel update crashes hard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This kernel update crashes my old machine (Intel Core i3-540, H55
  chipset) solid on boot. It needs to be powercycled. Selecting the
  previous kernel (3.13.0-139) in grub revives the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-139-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frontend   1899 F pulseaudio
frontend   2223 F mythfrontend.re
   /dev/snd/pcmC0D7p:   frontend   2223 F...m mythfrontend.re
  Date: Tue Jan 23 19:36:39 2018
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=258c1c48-dd3b-4e07-bc84-bdd38da7699d ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 ipv6.disable=1 splash quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-139-generic N/A
   linux-backports-modules-3.13.0-139-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2017-01-29 (359 days ago)
  WifiSyslog:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  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.:bvr080015:bd07/22/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1744995/+subscriptions

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

[Kernel-packages] [Bug 1743027] Re: error loading realtime clock since upgrading to 17.10

2018-01-23 Thread 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.15 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.15-rc9

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

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

** Tags added: needs-bisect

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

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-01-23 Thread Agustin Barto 
Output of dmidecode

** Attachment added: "dmidecode.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745032/+attachment/5041996/+files/dmidecode.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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  New

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745032] [NEW] AC adapter status not detected on Asus ZenBook UX410UAK

2018-01-23 Thread Agustin Barto 
Public bug reported:

The AC adapter status is incorrectly reported when the battery is fully
charged. It always shows as if the adapter is not plugged in. If the
battery is drained for a while, the adapter status is shown correctly
(both connects and disconnects are shown).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-31-generic 4.13.0-31.34
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  abarto 1388 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 18:26:18 2018
InstallationDate: Installed on 2018-01-23 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX410UAK
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-31-generic N/A
 linux-backports-modules-4.13.0-31-generic  N/A
 linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX410UAK.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX410UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX410UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

** Summary changed:

- AC adapter status not detected on Asus ZenBook ux410UAK
+ AC adapter status not detected on Asus ZenBook UX410UAK

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in linux package in Ubuntu:
  New

Bug description:
  The AC adapter status is incorrectly reported when the battery is
  fully charged. It always shows as if the adapter is not plugged in. If
  the battery is drained for a while, the adapter status is shown
  correctly (both connects and disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias:

[Kernel-packages] [Bug 1744712] Re: Dell XPS 13 9360 bluetooth (Atheros) won't connect after resume

2018-01-23 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Dell XPS 13 9360 bluetooth (Atheros) won't connect after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometimes after sleep/resume bluetooth won't reconnect to any device.

  I can see this in dmesg:
  [13129.890580] Bluetooth: hci0 command 0x0c1a tx timeout

  I tried:
  1. sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  2. tried reloading modules:
  sudo rmmod btusb
  sudo rmmod btrtl
  sudo rmmod hci_uart
  sudo rmmod btintel
  sudo rmmod btbcm btqca
  sudo rmmod rfcomm

  sleep 1

  sudo modprobe btusb btrtl hci_uart btintel btbcm btqca rfcomm

  no luck.

  3. restart bluetoothd - no luck

  Only reboot helps.

  Laptop is: Dell XPS 13 9360.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 22 12:50:58 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-18 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=e20224ee-6bcd-49a5-b911-a0c129a48da5 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:B6:D0:EB:95:A6  ACL MTU: 1024:8  SCO MTU: 50:8
DOWN 
RX bytes:2301887 acl:127559 sco:0 events:249 errors:0
TX bytes:4327 acl:47 sco:0 commands:81 errors:0

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

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

[Kernel-packages] [Bug 1744853] Re: 17.10.1 Cannot boot USB or CDROM or enter Bios

2018-01-23 Thread Joseph Salisbury 
*** This bug is a duplicate of bug 1734147 ***
https://bugs.launchpad.net/bugs/1734147

** This bug has been marked a duplicate of bug 1734147
   corrupted BIOS due to Intel SPI bug in 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/1744853

Title:
  17.10.1 Cannot boot USB or CDROM or enter Bios

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ACER V5-571G-53314G75Makk, SSID:23302770966

  Installed Ubuntu 17.10.1 yesterday and can longer boot into USB or
  CDROM. Cannot access BIOS(Phoenix) via F2.

  Ubuntu boots fine and works.

  I have followed the steps above in #1734147, installing both kernel
  versions and the BIOS has NOT recovered. I still cannot enter BIOS on
  this machine.

  Any assistance would be greatly appreciated.

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

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

[Kernel-packages] [Bug 1744852] Re: Broken screen after upgrading to 4.13.0-31.34~16.04.1

2018-01-23 Thread 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.15 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.15-rc9


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

** Tags added: kernel-da-key

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

Title:
  Broken screen after upgrading to 4.13.0-31.34~16.04.1

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  I've upgraded linux kernel from 4.10.0-42.46~16.04.1 to 4.13.0-31.34~16.04.1.
  After rebooting, my linux screen has been broken.

  See Imgur images.

  https://i.imgur.com/9cXTyIG.jpg
  https://i.imgur.com/0skgISl.jpg

  Restroing kernel 4.10, then works well.
  Also, 4.4.0-112.135 works well.

  --

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.3 LTS
  Release: 16.04
  Codename: xenial
  Linux asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 
UTC 2017 i686 i686 i686 GNU/Linux

  CPU: Single core Intel Atom N270 (-HT-) cache: 512 KB
     flags: (nx pae sse sse2 sse3 ssse3) bmips: 3192
     clock speeds: max: 1600 MHz 1: 1333 MHz 2: 800 MHz

  Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller
     bus-ID: 00:02.0
     Display Server: N/A drivers: intel (unloaded: fbdev,vesa)
     tty size: 80x24 Advanced Data: N/A out of X

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

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

[Kernel-packages] [Bug 1744875] Re: Enable Qlogic network drivers for installer

2018-01-23 Thread Joseph Salisbury 
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key

** Also affects: ubiquity (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/1744875

Title:
  Enable Qlogic network drivers for installer

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

Bug description:
  Not all Qlogic network drivers are enabled in the installer kernel (Ubuntu 
16.04) so detection
  of network interface fails during installer network dialog.

  Please enable this drivers:
  1) Add all E4 FastLinQ qed* drivers (qed, qede, qedr, qedi, qedf)
  2) Add all E3 FastLinQ bnx* drivers (bnx2, cnic, bnx2x, bnx2i, bnx2fc)

  qed and qede might already be enabled with a recent change:
  https://bugs.launchpad.net/yarmouth2/+bug/1743569

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

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

[Kernel-packages] [Bug 1744884] Re: OverlayFS not writeable

2018-01-23 Thread 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.15 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.15-rc9

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

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

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

Title:
  OverlayFS not writeable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A customer of ours has a collection of servers in a test environment which
  mounts production data via NFS. The NFS is then mounted as the lower directory
  of an overlayfs, $directory_workdir is mounted as the workdir, and
  $directory_cow is mounted as the upper directory. However, as of recent, the
  customer can not edit any data unless the necessary files are 'touch'ed first
  (or if you use vim, force-written).

  "uname -a" returns "Linux  4.4.0-104-generic #127-Ubuntu SMP Mon 
Dec
  11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux".

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

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

[Kernel-packages] [Bug 1744935] Re: [i915] Display Corruption

2018-01-23 Thread Joseph Salisbury 
Does the bug go away if you boot back into an older kernel, before the
updates?

** Tags added: kernel-da-key

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

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

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

Title:
  [i915] Display Corruption

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometime during a regular package update of Ubuntu of 17.10 I started
  having screen corruption issues within GL apps (e.g. WebGL on google
  maps) on both the external screens as well as the laptops (Thinkpad
  T460p), but then spread further to the regular desktop. I updated to
  Ubuntu 18.04 to try to resolve the issue and then even updated the
  kernel to the Linux-4.15-rc8 (4.15.0-994-generic) but the issues
  remain on both Wayland and Xorg. It seems related to the 3D
  acceleration since the corruption only starts with gdm, not on the
  framebuffer before. The issue happens on every boot. The i915 module
  is loaded with its default parameters, the nvidia card is deactivated
  with switcheroo and the proprietary driver has never been installed.

  The corruption is best described as flashing distortions associated
  with timers and/or input events. Sometimes a whole triangular section
  of up to a quarter of the double-screen setup is streched and/or
  discolored or blacked out. Sometimes black squares (a few pixels)
  splatter the whole screen for a few frames until a damaged region is
  updated. It looks like some kind of shader issue.

  Sometimes the screen gets stuck for a few seconds (presumably the hang
  from the crashdump attached), so it's possible that there are multiple
  issues but I can't discern them.

  dmesg reports:
  `
  [31026.161705] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [31731.589497] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [32477.060892] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [35533.800723] [drm] GPU HANG: ecode 9:0:0x85db, in gnome-shell [14269], 
reason: Hang on rcs0, action: reset
  [35533.800725] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [35533.800725] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [35533.800725] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [35533.800726] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [35533.800726] [drm] GPU crash dump saved to /sys/class/drm/card1/error
  [35533.800768] i915 :00:02.0: Resetting rcs0 after gpu hang
  [36101.847545] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [41209.093879] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [43073.711135] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [43339.548927] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [43886.208705] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [44617.864814] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [45925.860575] i915 :00:02.0: Resetting rcs0 after gpu hang
  `

  The memory size in UEFI is already set to the maximum of 512Mb.
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1396 F pulseaudio
abr1860 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=c566c6bc-3708-4170-8812-823802420564
  InstallationDate: Installed on 2017-05-30 (238 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 20FW003PMZ
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic

[Kernel-packages] [Bug 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured

2018-01-23 Thread Joseph Salisbury 
Can you see if this bug is resolved with the following artful kernel for bug 
1706247:
http://kernel.ubuntu.com/~jsalisbury/lp1706247/artful

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 
4.4.0-34-generic #53-Ubuntu
  [   57.553059] task: c0072773c8e0 ti: c0072778 task.ti: 
c0072778
  [   57.553067] NIP: c029bc04 LR: c029bbdc CTR: 
c01107f0
  [   57.553076] REGS: c00727783770 TRAP: 0300   Not tainted  
(4.4.0-34-generic)
  [   57.553083] MSR: 80019033   CR: 24242882  
XER: 0002
  [   57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 
SOFTE: 1 
  GPR00: c029bbdc c007277839f0 c15b5d00  
  GPR04: 0029d000 0800  fa01 
  GPR08: fa700020 0008 c185e270 c00e7e50 
  GPR12: 2200 ce6ea200 0029d000 2200 
  GPR16: 1000 c15e2200 0a70  
  GPR20: 0001 0100 0200 c15f16d0 
  GPR24: c1876510  0001 c1872a00 
  GPR28: 0029d000 f000 fa70 0029c000 
  [   57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220
  [   57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220
  [   57.553226] Call Trace:
  [   57.553231] [c007277839f0] [c029bbdc] 
dissolve_free_huge_pages+0x12c/0x220 (unreliable)
  [   57.553244] [c00727783a80] [c02dcbc8] 
__offline_pages.constprop.6+0x3f8/0x900
  [   57.553254] [c00727783bd0] [c06fbb38] 
memory_subsys_offline+0xa8/0x110
  [   57.553265] [c00727783c00] [c06d6424] 
device_offline+0x104/0x140
  [   57.553274] [c00727783c40] [c06fba80] 
store_mem_state+0x180/0x190
  [   57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0
  [   57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0
  [   57.553302] [c00727783d00] [c0397028] 
kernfs_fop_write+0x188/0x200
  [   57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0
  [   57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230
  [   57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110
  [   57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4
  [   57.553346] Instruction dump:
  [   57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 
fabe0020 
  [   57.553366] fade0028 79294620 79291764 7d234a14  3908 
f9030028 81091458 
  [   57.553383] ---[ end trace 617f7bdd75bcfc10 ]---
  [   57.557133] 
  Segmentation fault

  The following commit IDs were built into a 4.10.0-37-generic #41 test
  kernel and verified to fix the problem:

  a525108cf1cc14651602d678da38fa627a76a724
  e1073d1e7920946ac4776a619cc40668b9e1401b
  40692eb5eea209c2dd55857f44b4e1d7206e91d6
  e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d

[Kernel-packages] [Bug 1742675] Re: after upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all

2018-01-23 Thread Leszek 
Since it is probably due to Meltdown+Spectre patches we've probably
missed additional parameter - intel microcode used to build initramfs.
It has changed 2018-01-08 to new one but was changed back to old one
yesterday because many users reported boot and stability problems. It
for sure affects boot and generally "behavior". So to be sure that i use
correct microcode i've updated to lates on as of today and regenerated
all initramfs files fo all installed kernels doing:

sudo update-initramfs -u -k 4.4.0-112-generic

and so on for all kernels.

Now linux-image-4.4.0-112-generic works for me most of the time.
Sometimes it hangs during boot (about 1 in 3 boots) but once it boots
everything is ok and additionally Meltdown+Spectre is fully fixed
(according to checker script).

But still there are problems with latest versions of 4.10 and 4.13 kernels.
Mainline kernels work for me since they don't have all patches for 
Meltdown+Spectre (or even if they have them as a code, they need updated 
toolchain to be used to compile them to activate these patches but automated 
build system for mainline PPA doesn't support it for now).

It look in general like in my case (Asus Zenbook UX305FA with Intel Core
M-Y510) Meltdown+Spectre patches are OK when they are applied to 4.4
kernel but they break my laptop when applied to more recent kernels.

On the other hand every kernel works on my "big" PC with AMD Athlon.

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

Title:
  after upgrade to linux-image-extra-4.13.0-26-generic  the system does
  not start at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to linux-image-extra-4.13.0-26-generic  the system does not 
start at all.
  Only restart through Advanced Options with 
linux-image-extra-4.10.0-42-generic helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jan 11 15:20:26 2018
  InstallationDate: Installed on 2017-06-23 (201 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2017-06-24T18:05:02.372991

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

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

[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

2018-01-23 Thread Joseph Salisbury 
** No longer affects: linux (Ubuntu Xenial)

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

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

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

[Kernel-packages] [Bug 1743541] Re: Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is offline

2018-01-23 Thread Joseph Salisbury 
There is a ppc64 tools package there now.  Can you see if that package
works for you?

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

Title:
  Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is
  offline

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:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-16 
04:58:48 ==
  Problem Description :
  =

  cpupower monitor fails to show stop states when cpu 0 is made offline.

  Testing :
  =
  root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# 

  root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop | stop | stop 
 0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.01

  Details :
  
  uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 
21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  OS : Ubuntu 18.04
  Machine : Witherspoon ( DD2.1) and Boston (DD.01)

  Patch :
  
  Patch that fixes the issue : 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  == Comment: #1 - VIPIN K. PARASHAR  - 2018-01-16 
05:09:40 ==
  (In reply to comment #0)

  > Patch :
  > 
  > Patch that fixes the issue :
  > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
  > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  $ git log dbdc468f35ee827 -1
  commit dbdc468f35ee827cab2753caa1c660bdb832243a
  Author: Abhishek Goel 
  Date:   Wed Nov 15 14:10:02 2017 +0530

  cpupower : Fix cpupower working when cpu0 is offline
  
  cpuidle_monitor used to assume that cpu0 is always online which is not
  a valid assumption on POWER machines. This patch fixes this by getting
  the cpu on which the current thread is running, instead of always using
  cpu0 for monitoring which may not be online.
  
  Signed-off-by: Abhishek Goel 
  Signed-off-by: Shuah Khan 
  $

  Commit dbdc468f3 is available with 4.15-rc2 onwards.

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

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

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

2018-01-23 Thread Josep Pujadas-Jubany 
Updated BIOS to 1.13 & 1.15 doesn't hel for Acer TravelMate B117-M (SSD
disk).

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

Title:
  Unstable LTS kernel 4.13.0-26

Status in linux-signed package in Ubuntu:
  Confirmed

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

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

  unexpected irq trap at vector

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

  At home (no signed kernel, old machine) my VirtualBox freezes also the
  machine, as explained at
  https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14

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

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

Re: [Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2018-01-23 Thread Ian Bruntlett 
Hi Tom,

On 23 January 2018 at 19:02, tom  wrote:

> With my Ubuntu version 16.04 LTS i didn't have the problem, until recently!
> I suspect with an update from kernel 4.10.x to 4.13.x
> So I manually removed the kernel image and headers from version 4.13.x,
> thereby in fact downgrading again to the older kernel, fixing my problem.
> So this confirms the statement above that kernel 4.13 is a problematic one.
>

Ubuntu keeps more than one kernel on the hard drive. It defaults to using
the most current one.

You can choose which Linux kernel to boot from by using the GRUB menu on
booting.

To do that, switch your computer on, and, as soon as you see the
manufacturer's logo (i.e. the BIOS screen), press and hold down the
right-hand SHIFT key.

You should then see a menu with a title at the top that reads like "GNU
GRUB version" (etc). This is where you can do quite a few things. Use the
down arrow key to select "Advanced Options for Ubuntu". This takes you to a
screen where you choose a kernel to boot or choose to boot a particular
kernel in"recovery mode".

The command "uname -a" gives info on the current running kernel.

The command "lsb_release -a" gives distro-specific info.

HTH,


Ian

-- 
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page - https://sites.google.com/site/
ianbruntlett/home/free-software

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1745007] Re: Support cppc-cpufreq driver on ThunderX2 systems

2018-01-23 Thread dann frazier 
** Description changed:

  [Impact]
  The cppc-cpufreq driver fails to initialize on ThunderX2 systems, which is 
used to communicate power configuration to firmware.
  
  [Test Case]
- sudo modprobe cppc-cpufree || echo "Fail"
+ sudo modprobe cppc-cpufreq || echo "Fail"
  
  [Regression Risk]
  The fix consists of clean cherry-picks from upstream that are restricted to a 
single driver. Regressions would therefore be restricted to platforms that 
support ACPI CPPC power management.

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

Title:
  Support cppc-cpufreq driver on ThunderX2 systems

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

Bug description:
  [Impact]
  The cppc-cpufreq driver fails to initialize on ThunderX2 systems, which is 
used to communicate power configuration to firmware.

  [Test Case]
  sudo modprobe cppc-cpufreq || echo "Fail"

  [Regression Risk]
  The fix consists of clean cherry-picks from upstream that are restricted to a 
single driver. Regressions would therefore be restricted to platforms that 
support ACPI CPPC power management.

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

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

[Kernel-packages] [Bug 1745007] [NEW] Support cppc-cpufreq driver on ThunderX2 systems

2018-01-23 Thread dann frazier 
Public bug reported:

[Impact]
The cppc-cpufreq driver fails to initialize on ThunderX2 systems, which is used 
to communicate power configuration to firmware.

[Test Case]
sudo modprobe cppc-cpufreq || echo "Fail"

[Regression Risk]
The fix consists of clean cherry-picks from upstream that are restricted to a 
single driver. Regressions would therefore be restricted to platforms that 
support ACPI CPPC power management.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: dann frazier (dannf)
   Status: In Progress

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

Title:
  Support cppc-cpufreq driver on ThunderX2 systems

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

Bug description:
  [Impact]
  The cppc-cpufreq driver fails to initialize on ThunderX2 systems, which is 
used to communicate power configuration to firmware.

  [Test Case]
  sudo modprobe cppc-cpufreq || echo "Fail"

  [Regression Risk]
  The fix consists of clean cherry-picks from upstream that are restricted to a 
single driver. Regressions would therefore be restricted to platforms that 
support ACPI CPPC power management.

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

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

[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2018-01-23 Thread Angelo Lisco 
Hi Alexander. Thanks for your bug report and all your effort to troubleshoot 
and fix this weird issue.
I'm not using any docking station but I'm experiencing the same behaviour 
(screen flickering and unable to lock my screen) here on a Lenovo T450s with a 
Intel HD Graphics 5500 (Broadwell GT2) GPU. 
It happens both with Ubuntu 17.10 and Fedora (26 and 27) so i'm so I suppose 
that's a weird bug in the intel driver. 
Did you find any workaround or fix?

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

2018-01-23 Thread Angelo Lisco 
Same issue here on a Lenovo T450s with a Intel HD Graphics 5500 (Broadwell GT2) 
GPU. It happens both with Ubuntu 16.04 and Fedora (26 and 27) so I suppose 
that's a weird bug in the intel driver.
It also happens sometimes without any external monitor when I leave my notebook 
powered up during the night: in the moring my gdm lock screen flickers and I'm 
unable to login into my session.
Has someone found a workaround or a fix?

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2018-01-23 Thread tom 
With my Ubuntu version 16.04 LTS i didn't have the problem, until recently!
I suspect with an update from kernel 4.10.x to 4.13.x
So I manually removed the kernel image and headers from version 4.13.x, thereby 
in fact downgrading again to the older kernel, fixing my problem.
So this confirms the statement above that kernel 4.13 is a problematic one.

best regards
Tom

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

2018-01-23 Thread Ubuntu Kernel Bot 
This change was made by a bot.

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

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

Title:
  Spectre kernel update crashes hard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This kernel update crashes my old machine (Intel Core i3-540, H55
  chipset) solid on boot. It needs to be powercycled. Selecting the
  previous kernel (3.13.0-139) in grub revives the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-139-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frontend   1899 F pulseaudio
frontend   2223 F mythfrontend.re
   /dev/snd/pcmC0D7p:   frontend   2223 F...m mythfrontend.re
  Date: Tue Jan 23 19:36:39 2018
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=258c1c48-dd3b-4e07-bc84-bdd38da7699d ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 ipv6.disable=1 splash quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-139-generic N/A
   linux-backports-modules-3.13.0-139-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2017-01-29 (359 days ago)
  WifiSyslog:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  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.:bvr080015:bd07/22/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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/1744995/+subscriptions

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

[Kernel-packages] [Bug 1744995] [NEW] Spectre kernel update crashes hard

2018-01-23 Thread JanCeuleers 
Public bug reported:

This kernel update crashes my old machine (Intel Core i3-540, H55
chipset) solid on boot. It needs to be powercycled. Selecting the
previous kernel (3.13.0-139) in grub revives the machine.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-141-generic 3.13.0-141.190
ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
Uname: Linux 3.13.0-139-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  frontend   1899 F pulseaudio
  frontend   2223 F mythfrontend.re
 /dev/snd/pcmC0D7p:   frontend   2223 F...m mythfrontend.re
Date: Tue Jan 23 19:36:39 2018
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=258c1c48-dd3b-4e07-bc84-bdd38da7699d ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 ipv6.disable=1 splash quiet
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-139-generic N/A
 linux-backports-modules-3.13.0-139-generic  N/A
 linux-firmware  1.127.24
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2017-01-29 (359 days ago)
WifiSyslog:
 
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
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.:bvr080015:bd07/22/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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.

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


** Tags: amd64 apport-bug trusty

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

Title:
  Spectre kernel update crashes hard

Status in linux package in Ubuntu:
  New

Bug description:
  This kernel update crashes my old machine (Intel Core i3-540, H55
  chipset) solid on boot. It needs to be powercycled. Selecting the
  previous kernel (3.13.0-139) in grub revives the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-139-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frontend   1899 F pulseaudio
frontend   2223 F mythfrontend.re
   /dev/snd/pcmC0D7p:   frontend   2223 F...m mythfrontend.re
  Date: Tue Jan 23 19:36:39 2018
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-139-generic 
root=UUID=258c1c48-dd3b-4e07-bc84-bdd38da7699d ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 ipv6.disable=1 splash quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-139-generic N/A
   linux-backports-modules-3.13.0-139-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2017-01-29 (359 days ago)
  WifiSyslog:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  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.:bvr080015:bd07/22/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1744979] ProcCpuinfoMinimal.txt

2018-01-23 Thread csola48 
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1744979/+attachment/5041909/+files/ProcCpuinfoMinimal.txt

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1744979] Lsusb.txt

2018-01-23 Thread csola48 
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1744979/+attachment/5041907/+files/Lsusb.txt

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1744979/+attachment/5041905/+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/1744979

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1744117] Re: [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel

2018-01-23 Thread Eric Desrochers 
Patch submitted to the kernel team ML

[PATCH][SRU][X] ALSA: hda - Add missing NVIDIA GPU codec IDs to patch
table

- Eric

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

Title:
  [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table
  to Ubuntu 16.04 LTS Kernel

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

Bug description:
  Add support for 4/6/8 channel sound in 16.04 LTS kernel for future
  GPUs.

  This commit[1] first introduced in "Thu Jul 13 19:27:39 2017"[2] has
  what is needed base on discussion we had with nvidia:

  [1] - Commit
   
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f

  ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

  Add codec IDs for several recently released, pending, and historical
  NVIDIA GPU audio controllers to the patch table, to allow the correct
  patch functions to be selected for them.

  [2] - git describe --contains 74ec118152ea494a25ebb677cbc83a75c982ac5f
  v4.13-rc3~21^2~5

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

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

2018-01-23 Thread csola48 
apport information

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-112-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1744979] Re: grub_efi_secure_boot signal at the beginning of the boot process

2018-01-23 Thread csola48 
apport information

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

** Tags added: apport-collected

** Description changed:

  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot
  
  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  
  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit
  
  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: i386
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  csola481454 F pulseaudio
+  /dev/snd/controlC2:  csola481454 F pulseaudio
+  /dev/snd/controlC0:  csola481454 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
+ InstallationDate: Installed on 2016-11-08 (441 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp4s0no wireless extensions.
+ MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
+ NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=4cbb9ed4-c9ab-4ee3-8eb5-2473af0d2ae7 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-112-generic N/A
+  linux-backports-modules-4.4.0-112-generic  N/A
+  linux-firmware 1.157.14
+ RfKill:
+  
+ Tags:  xenial
+ Uname: Linux 4.4.0-112-generic i686
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/21/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F7
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: H77-DS3H
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  csola481454 F pulseaudio
   /dev/snd/controlC2:  csola481454 F pulseaudio
   /dev/snd/controlC0:  csola481454 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6c8c77a4-d4d3-4e31-a038-13930e1abfd0
  InstallationDate: Installed on 2016-11-08 (441 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType:

[Kernel-packages] [Bug 1744117] Re: [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel

2018-01-23 Thread Eric Desrochers 
I have provided a test kernel "4.4.0-111-generic
#134+hf166707v20180117b5" for pre-SRU verification and it has been
brought to my attention the following statement:

-
Our QA was able to test with the kernel you provided, and things look good!

I've upgraded the kernel and issue did not repro.

Config :
GPU Driver 384.111
Kernel 4.4.0-111-generic

# uname -a
Linux  4.4.0-111-generic #134+hf166707v20180117b5-Ubuntu SMP Wed Jan 
17 19:04:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I've verified output through all channels (7.1) using Test Sound option in 
Sound Setting + by running different 4,6 channel clips using aplay.
Connections were made using DP-HDMI dongle (accell) + DENON-AVR
-

- Eric

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

Title:
  [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table
  to Ubuntu 16.04 LTS Kernel

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

Bug description:
  Add support for 4/6/8 channel sound in 16.04 LTS kernel for future
  GPUs.

  This commit[1] first introduced in "Thu Jul 13 19:27:39 2017"[2] has
  what is needed base on discussion we had with nvidia:

  [1] - Commit
   
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f

  ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

  Add codec IDs for several recently released, pending, and historical
  NVIDIA GPU audio controllers to the patch table, to allow the correct
  patch functions to be selected for them.

  [2] - git describe --contains 74ec118152ea494a25ebb677cbc83a75c982ac5f
  v4.13-rc3~21^2~5

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

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

2018-01-23 Thread Scott Emmons 
Confirmed to also affect bionic:

$ sudo journalctl -u zfs-import-cache.service
-- Logs begin at Tue 2018-01-23 17:46:55 UTC, end at Tue 2018-01-23 17:49:18 
UTC. --
Jan 23 17:46:58 ubuntu systemd[1]: Starting Import ZFS pools by cache file...
Jan 23 17:46:59 ubuntu zpool[640]: failed to open cache file: No such file or 
directory
Jan 23 17:46:59 ubuntu systemd[1]: zfs-import-cache.service: Main process 
exited, code=exited, status=1/FAILURE
Jan 23 17:46:59 ubuntu systemd[1]: zfs-import-cache.service: Failed with result 
'exit-code'.
Jan 23 17:46:59 ubuntu systemd[1]: Failed to start Import ZFS pools by cache 
file.

This is on a host with no ZFS filesystems, so expected behavior is a no-
op.

** Tags added: artful bionic

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

[Kernel-packages] [Bug 1726743] Re: Kernel hangs after mounting usb HD

2018-01-23 Thread Wolf Rogner 
Kernel 4.13.0.31.33 still has this issue.

Machine simply panics and freezes.

syslog:

...
Jan 23 16:40:49 mbpr13b kernel: [12217.671240] usb 2-2: new SuperSpeed USB 
device number 5 using xhci_hcd
Jan 23 16:40:49 mbpr13b kernel: [12217.692311] usb 2-2: New USB device found, 
idVendor=0bc2, idProduct=231a
Jan 23 16:40:49 mbpr13b kernel: [12217.692315] usb 2-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Jan 23 16:40:49 mbpr13b kernel: [12217.692317] usb 2-2: Product: Expansion
Jan 23 16:40:49 mbpr13b kernel: [12217.692319] usb 2-2: Manufacturer: Seagate
Jan 23 16:40:49 mbpr13b kernel: [12217.692321] usb 2-2: SerialNumber: NA8658H8
Jan 23 16:40:49 mbpr13b kernel: [12217.694135] scsi host1: uas
Jan 23 16:40:49 mbpr13b kernel: [12217.694460] scsi 1:0:0:0: tag#0 data cmplt 
err -75 uas-tag 1 inflight: CMD 
Jan 23 16:40:49 mbpr13b kernel: [12217.694463] scsi 1:0:0:0: tag#0 CDB: Inquiry 
12 00 00 00 24 00
Jan 23 16:40:49 mbpr13b kernel: [12217.694470] usb 2-2: stat urb: no pending 
cmd for uas-tag 0
Jan 23 16:40:50 mbpr13b kernel: [12217.695541] BUG: unable to handle kernel 
paging request at 0103
Jan 23 16:40:50 mbpr13b kernel: [12217.695604] IP: __kmalloc+0x9b/0x200
Jan 23 16:40:50 mbpr13b kernel: [12217.695629] PGD 0 
Jan 23 16:40:50 mbpr13b kernel: [12217.695630] P4D 0 
Jan 23 16:40:50 mbpr13b kernel: [12217.695646] 
Jan 23 16:40:50 mbpr13b kernel: [12217.695674] Oops:  [#1] SMP PTI
Jan 23 16:40:50 mbpr13b kernel: [12217.695698] Modules linked in: pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm hid_magicmouse 
hidp cmac bnep nls_iso8859_1 joydev bcm5974 btusb btrtl btbcm btintel 
input_leds bluetooth ecdh_generic applesmc snd_hda_codec_cirrus 
snd_hda_codec_hdmi snd_hda_codec_generic input_polldev snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel snd_pcm snd_seq_midi snd_seq_midi_event kvm 
snd_rawmidi snd_seq snd_seq_device irqbypass snd_timer intel_cstate 
intel_rapl_perf snd brcmfmac intel_pch_thermal lpc_ich brcmutil soundcore 
thunderbolt cfg80211 bdc_pci mei_me dw_dmac_pci mei dw_dmac_core shpchp 
spi_pxa2xx_pci sbs acpi_als sbshc kfifo_buf industrialio spi_pxa2xx_platform 
mac_hid apple_bl parport_pc ppdev lp parport ip_tables
Jan 23 16:40:50 mbpr13b kernel: [12217.696152]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt hid_apple hid_generic usbhid hid uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel 
i2c_algo_bit aes_x86_64 crypto_simd drm_kms_helper glue_helper cryptd 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video
Jan 23 16:40:50 mbpr13b kernel: [12217.696339] CPU: 0 PID: 403 Comm: 
systemd-journal Tainted: G   OE   4.13.0-31-generic #34-Ubuntu
Jan 23 16:40:50 mbpr13b kernel: [12217.696396] Hardware name: Apple Inc. 
MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS MBP121.88Z.0171.B00.1708080033 
08/08/2017
Jan 23 16:40:50 mbpr13b kernel: [12217.696461] task: 8f3d10d7c5c0 
task.stack: a44f81f24000
Jan 23 16:40:50 mbpr13b kernel: [12217.696501] RIP: 0010:__kmalloc+0x9b/0x200
Jan 23 16:40:50 mbpr13b kernel: [12217.696529] RSP: 0018:a44f81f27c18 
EFLAGS: 00010206
Jan 23 16:40:50 mbpr13b kernel: [12217.696563] RAX:  RBX: 
014080c0 RCX: 001007a8
Jan 23 16:40:50 mbpr13b kernel: [12217.696607] RDX: 001007a7 RSI: 
 RDI: 00025ce0
Jan 23 16:40:50 mbpr13b kernel: [12217.696651] RBP: a44f81f27c48 R08: 
8f3d2ec25ce0 R09: 8f3d1e003980
Jan 23 16:40:50 mbpr13b kernel: [12217.696695] R10: a44f81f27ec0 R11: 
 R12: 0103
Jan 23 16:40:50 mbpr13b kernel: [12217.696739] R13: 014080c0 R14: 
0018 R15: 8f3d1e003980
Jan 23 16:40:50 mbpr13b kernel: [12217.696784] FS:  7f41614fddc0() 
GS:8f3d2ec0() knlGS:
Jan 23 16:40:50 mbpr13b kernel: [12217.696833] CS:  0010 DS:  ES:  CR0: 
80050033
Jan 23 16:40:50 mbpr13b kernel: [12217.696869] CR2: 0103 CR3: 
0004516a2002 CR4: 003606f0
Jan 23 16:40:50 mbpr13b kernel: [12217.696914] DR0:  DR1: 
 DR2: 
Jan 23 16:40:50 mbpr13b kernel: [12217.696957] DR3: 0080 DR6: 
0ff0 DR7: 2400
Jan 23 16:40:50 mbpr13b kernel: [12217.697001] Call Trace:
Jan 23 16:40:50 mbpr13b kernel: [12217.697023]  ? security_file_alloc+0x58/0x70
Jan 23 16:40:50 mbpr13b kernel: [12217.697053]  security_file_alloc+0x58/0x70
Jan 23 16:40:50 mbpr13b kernel: [12217.697083]  get_empty_filp+0x93/0x1b0
Jan 23 16:40:50 mbpr13b kernel: [12217.697111]  path_openat+0x3d/0x1630
Jan 23 16:40:50 mbpr13b kernel: [12217.697139]  ? __bpf_prog_run32+0x39/0x50
Jan 23 16:40:50 mbpr13b kernel: [12217.697167]  ? putname+0x4b/0x50
Jan 23 16:40:50 mbpr13b kernel: [12217.697192]  do_filp_open+0x9b/0x110
Jan 23 16:40:50 mbpr13b kernel: [12217.697219]  ?

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

2018-01-23 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

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

2018-01-23 Thread Kenan Gutić 
My laptop: Mediacom Smartbook 14 Ultra M-SB14UC is fixed with official
fix provided in description of this bug report. Thank you <3

** Description changed:

  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.
  
  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.
  
  ---
  
  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the
  kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.
  
  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:
  
  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.
  
  After your BIOS is fixed, the kernel packages you just installed are no
  longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.
  
  The patch used to build the linux v4.15 kernel in step 8 can be found at
  https://goo.gl/xUKJFR.
  
  ---
  
  Test Case: Fix has been verified by our HWE team on affected hardware.
  
  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.
  
  ---
  
  Affected Machines:
  
  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY
  
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
- Mediacom Smartbook 14 Ultra M-SB14UC
+ Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la
  
  ---
  
  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018
  
  ---
  
  Original Description:
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

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

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

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

  ---

  Fix: The issue was fixed in kernel version

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

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

apport-collect 1744979

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

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

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...

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

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

[Kernel-packages] [Bug 1744981] Re: linux: 4.14.0-17.20 -proposed tracker

2018-01-23 Thread Brad Figg 
** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.14.0-17.20 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
+ 
+ kernel-phase:Packaging
+ kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC

** Description changed:

  This bug is for tracking the 4.14.0-17.20 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
  
  kernel-phase:Packaging
  kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.14.0-17.20 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-17.20 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

  kernel-phase:Packaging
  kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1743799] Re: "fwts uefirtmisc" causes reboot in recent kernels

2018-01-23 Thread Rod Smith 
A further update: This problem does NOT occur under Artful on the Dell
PowerEdge T610 with the following kernel:

$ uname -a
Linux hogplum 4.13.0-30-generic #33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

I have not yet tested with Xenial or with other kernel series on the
PowerEdge T710.

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

Title:
  "fwts uefirtmisc" causes reboot in recent kernels

Status in Provider for Plainbox - Checkbox:
  Invalid
Status in linux package in Ubuntu:
  Triaged

Bug description:
  In doing Meltdown regression testing, we found that one server,
  lucuma, a Dell PowerEdge T710, would spontaneously reboot when running
  the miscellanea/fwts_test under Ubuntu 14.04.5 with a
  3.13.0-139-generic #188-Ubuntu kernel. This test has been dropped from
  our test list for 16.04, so it was not initially tested under more
  recent kernels. This server has been out of our testing queue for
  years, so it hasn't been tested since Ubuntu 10.04. Thus, we don't yet
  know if the problem is a regression or if it's existed for a long
  time. We need to do more testing to better isolate the issue; stay
  tuned for more information

  The system's entry on C3 is:

  https://certification.canonical.com/hardware/200910-4539/

  The submission showing the error is:

  https://certification.canonical.com/hardware/200910-4539/submission/126589/

To manage notifications about this bug go to:
https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1743799/+subscriptions

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

[Kernel-packages] [Bug 1734901] Re: linux: 4.14.0-10.12 -proposed tracker

2018-01-23 Thread Seth Forshee 
*** This bug is a duplicate of bug 1744981 ***
https://bugs.launchpad.net/bugs/1744981

** This bug is no longer a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker
** This bug has been marked a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker

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

Title:
  linux: 4.14.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-10.12 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

  kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1738848] Re: linux: 4.14.0-13.15 -proposed tracker

2018-01-23 Thread Seth Forshee 
*** This bug is a duplicate of bug 1744981 ***
https://bugs.launchpad.net/bugs/1744981

** This bug is no longer a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker
** This bug has been marked a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker

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

Title:
  linux: 4.14.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-13.15 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 --
  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-development-workflow/+bug/1738848/+subscriptions

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

[Kernel-packages] [Bug 1734695] Re: linux: 4.14.0-8.10 -proposed tracker

2018-01-23 Thread Seth Forshee 
*** This bug is a duplicate of bug 1744981 ***
https://bugs.launchpad.net/bugs/1744981

** This bug is no longer a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker
** This bug has been marked a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker

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

Title:
  linux: 4.14.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-8.10 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

  kernel-phase:Packaging
  kernel-phase-changed:Monday, 27. November 2017 14:00 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1736168] Re: linux: 4.14.0-11.13 -proposed tracker

2018-01-23 Thread Seth Forshee 
*** This bug is a duplicate of bug 1744981 ***
https://bugs.launchpad.net/bugs/1744981

** This bug is no longer a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker
** This bug has been marked a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker

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

Title:
  linux: 4.14.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-11.13 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 --
  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-development-workflow/+bug/1736168/+subscriptions

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

[Kernel-packages] [Bug 1741920] Re: linux: 4.14.0-16.19 -proposed tracker

2018-01-23 Thread Seth Forshee 
*** This bug is a duplicate of bug 1744981 ***
https://bugs.launchpad.net/bugs/1744981

** This bug has been marked a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker

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

Title:
  linux: 4.14.0-16.19 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-16.19 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 --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1738554] Re: linux: 4.14.0-12.14 -proposed tracker

2018-01-23 Thread Seth Forshee 
*** This bug is a duplicate of bug 1744981 ***
https://bugs.launchpad.net/bugs/1744981

** This bug is no longer a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker
** This bug has been marked a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker

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

Title:
  linux: 4.14.0-12.14 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-12.14 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

  kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying

2018-01-23 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  QCA6174 stops working on newer kernels after second group rekeying

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Artful:
  Confirmed

Bug description:
  After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my
  WiFi would stop working after every 20 minutes or so. The problem
  initially seems related to some DNS services crashing because of what
  happend in browsers and other software that usually rely on DNS but
  I've noticed I couldn't ping my router and other local devices for
  which I knew the IP addresses. The connection is still presented as
  being connected, but it just doesn't work.

  After googling a lot, I came across this question on askubuntu.com

  https://askubuntu.com/questions/967355/wifi-unstable-
  after-17-10-update

  Which led me to this bug report on Debian's bug tracker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184

  Which led me to this bug in upstream:

  http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html

  I've tested the proposed fixes myself and I can confirm they work.

  What causes the WiFi to stop working is a bug related to the group
  rekeying routines.

  It seems it only happens in >4.12 kernels, hence why I've only had
  problems after 4.13 was pushed as the current rolling HWE kernel for
  16.04.3.

  kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1
  of the firmware-6.bin file, which is the current one present in
  upstream.

  Updating the firmware-6.bin (and board-2.bin, optionally) to any
  version equal or later than that fixes the issue completely.

  -

  SRU Justification:
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in 
numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, 
silently stops working after the second group rekeying, which is usually few 
minutes after the user has connected to a WiFi network. The connection status 
remains unchanged but there's no connectivity at all. This effectively 
disconnects the user without notifying it of what's occurred.

  Additionally, this happens for the only HWE kernel that's been patched
  against the recent Meltdown vulnerability, leaving the user without
  the option of using a recent kernel and a secure kernel at the same
  time.

  [Test Case]
  After applying the required firmwares, check if the connectivity is 
unaffected after the second group rekeying, which can be checked with

  $ cat /var/log/syslog | grep wpa_.*rekeying

  [How to fix it]

  Update the firmware-6.bin file to version
  WLAN.RM.4.4.1-00051-QCARMSWP-1 or later.

  [Regression Potential]
  The new firmware overwrites the old one, but since it's been in upstream 
since October 2017, it should be good.

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-firmware:
    Instalado: 1.157.14
    Candidato: 1.157.14
    Tabela de versão:
   *** 1.157.14 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

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

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

[Kernel-packages] [Bug 1741501] Re: linux: 4.14.0-15.18 -proposed tracker

2018-01-23 Thread Seth Forshee 
*** This bug is a duplicate of bug 1744981 ***
https://bugs.launchpad.net/bugs/1744981

** This bug is no longer a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker
** This bug has been marked a duplicate of bug 1744981
   linux: 4.14.0-17.20 -proposed tracker

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

Title:
  linux: 4.14.0-15.18 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-15.18 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 --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-01-23 Thread J L 
I know it might sound stupid, but how do I get a terminal session as I
am not able to log in under X11 at all when this issue occurs. It boots
straight away into bios.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1744981] [NEW] linux: 4.14.0-17.20 -proposed tracker

2018-01-23 Thread Seth Forshee 
Public bug reported:

This bug is for tracking the 4.14.0-17.20 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

kernel-phase:Packaging
kernel-phase-changed:Tuesday, 23. January 2018 17:30 UTC

-- swm properties --
phase: Packaging

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: bionic

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

[Kernel-packages] [Bug 1744979] [NEW] grub_efi_secure_boot signal at the beginning of the boot process

2018-01-23 Thread csola48 
Public bug reported:

The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
The first message always: grub_efi_secure_boot

Ubuntu 4.4.0-112.135-generic 4.4.98
LSB Version:
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
GeForce GT 630/PCIe/SSE2
system 32 bit

Please help... 
I chose 16.04 LTS because I wanted to have a long, calm and safe use ...

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

** Attachment added: "20180123_143559.jpg"
   
https://bugs.launchpad.net/bugs/1744979/+attachment/5041851/+files/20180123_143559.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/1744979

Title:
  grub_efi_secure_boot signal at the beginning of the boot process

Status in linux package in Ubuntu:
  New

Bug description:
  The previous kernel (4.4.0-109) was running without any problems, without 
triggering an error.
  After today's kernel update, the machine can not be started unless you select 
"run" the selected kernel from the advanced settings menu item.
  The first message always: grub_efi_secure_boot

  Ubuntu 4.4.0-112.135-generic 4.4.98
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  Intel® Core™ i5-3330 CPU @ 3.00GHz × 4 
  GeForce GT 630/PCIe/SSE2
  system 32 bit

  Please help... 
  I chose 16.04 LTS because I wanted to have a long, calm and safe use ...

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2018-01-23 Thread 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/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  Fix Committed
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  In Progress
Status in open-iscsi source package in Trusty:
  Opinion
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

 $ systemctl edit --full open-iscsi.service
 ...
 #ExecStop=/lib/open-iscsi/logout-all.sh
 ...

 $ sudo reboot # this will make server to hang forever
   # on shutdown

  [Regression Potential]

   * the regression is low because the change acts on the iscsi
 transport layer code ONLY when the server is in shutdown 
 state.

   * any error in logic would only appear during shutdown and
 would not cause any harm to data.

  [Other Info]
   
   * ORIGINAL BUG DESCRIPTION

  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-01-23 Thread Raymond Wan 
I spoke too soon!  The recent 4.13.0-31 kernel appears to have fixed the 
problem for me, at least.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1730152] Re: Internal microsd card reader does not work in Ubuntu 17.10

2018-01-23 Thread Bao Pham 
Please someone write the driver for this card reader.

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

Title:
  Internal microsd card reader does not work in Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 x86_64 of Wayland-Session is running on a HP Envy
  13-ad1xx notbook with a internal microsd card reader. The system gives
  no response when inserting different micro sd cards, which work fine
  on Windows 10. I report this bug in hope that the upstream may notice
  and make some change on the suited driver or kernel module. I would
  provide more information under further direction.

  According to `lspci` output, the model name is 'Alcor Micro Device
  6625'.

  `udevadm monitor --env` gives no related events when inserting or
  pulling out the microsd card, in which only thermal_zone changes are
  recorded. No related events are recoded in /var/log/kern.log either.

  With sd card being inserted, `sudo fdisk -l` and `sudo blkid` gives no
  related information. The outputs are all about partitions on the local
  disk. No sdhc or mmc device is found in /dev/ either.

  The only implication now is the system notice the existence of the
  card reader, in terms of `lspci` outputs, the '01:00.0 Unassigned
  class [ff00]: Alcor Micro Device 6625', even when a sd card is
  inserted:

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   limorg 1514 F...m pulseaudio
   /dev/snd/controlC0:  limorg 1514 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 10:29:26 2017
  HibernationDevice: RESUME=UUID=8f370e7c-280d-4864-b687-a2c81ce87247
  InstallationDate: Installed on 2017-10-22 (13 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:5620 Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Laptop 13-ad1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=67e321d1-4810-4157-8c29-09c51ea7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-29 (6 days ago)
  dmi.bios.date: 07/26/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 39.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd07/26/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A8:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ad1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work

2018-01-23 Thread Vadim Fedosov 
Confirm. I have updated 17.04 -> 17.10 and this bug is still exist. Have
to edit hid2hci.rules file as Daniel Beauyat suggest to get it work.
Have this bug since I start using ubuntu 10.04.

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

Title:
  Bluetooth Logitech Dinovo Keyboard/Mouse don't work

Status in Bluez Utilities:
  New
Status in Bluez-utils:
  New
Status in Linux Mint:
  Invalid
Status in Unity:
  Invalid
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Invalid

Bug description:
  Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will 
work until Nautilus starts.  After Nautilus starts the keyboard and mouse are 
unresponsive and do not work.
  I tried reconnecting the keyboard and mouse by using the discovery buttons on 
both the Bluetooth Dongle and Input device.  The problem still persists.
  Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. 
 Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech 
mini bluetooth receiver.

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

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

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

2018-01-23 Thread bugproxy 
--- Comment From dieg...@br.ibm.com 2018-01-23 09:23 EDT---
Hi Joseph,

I was able to reproduce the problem on HWE Kernal (XENIAL):

-- System

root@tuletapio2-lp3:~# uname -a
Linux tuletapio2-lp3 4.13.13 #1 SMP Tue Jan 23 07:41:39 CST 2018 ppc64le 
ppc64le ppc64le GNU/Linux

root@tuletapio2-lp3:~# cat /proc/meminfo
HugePages_Total:   2
HugePages_Free:2
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   16777216 kB

root@tuletapio2-lp3:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.13.13 root=UUID=728bebfe-83ba-410d-917b-b552edbbb0a3 
ro quiet splash default_hugepagesz=16G hugepagesz=16G hugepages=2

-- DUMP
Unable to handle kernel paging request for data at address 0x5deadbeef108
Faulting instruction address: 0xc02cf374
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=2048
NUMA
pSeries
Modules linked in:
CPU: 7 PID: 3769 Comm: mem-on-off-test Not tainted 4.13.13 #1
task: c007d940 task.stack: c007d948
NIP: c02cf374 LR: c02cf298 CTR: c0134ef0
REGS: c007d94837d0 TRAP: 0380   Not tainted  (4.13.13)
MSR: 8280b033 
CR: 44422484  XER: 
CFAR: c02cf308 SOFTE: 1
GPR00: c02cf28c c007d9483a50 c0e6ff00 c0fbc580
GPR04: f400 5deadbeef100 5deadbeef200 0002
GPR08: 5deadbeef000 0001 c0fbc580 c007fb000628
GPR12: 2200 cfd02a00 1000 f400
GPR16: 0002  c0ea3b00 1000
GPR20: db4f 0001 c00fffd44600 c007d9483b60
GPR24: 0010 c0f0dad8 c0eb2dd0 0001
GPR28:  c0fc4580 c0fd4580 f400
NIP [c02cf374] dissolve_free_huge_page+0x124/0x230
LR [c02cf298] dissolve_free_huge_page+0x48/0x230
Call Trace:
[c007d9483a50] [c02cf28c] dissolve_free_huge_page+0x3c/0x230 
(unreliable)
[c007d9483a90] [c02cf548] dissolve_free_huge_pages+0xc8/0x150
[c007d9483ae0] [c02ee1c8] __offline_pages.constprop.5+0x398/0xa90
[c007d9483c30] [c0645870] memory_subsys_offline+0x60/0xf0
[c007d9483c60] [c0623434] device_offline+0xf4/0x130
[c007d9483ca0] [c0645718] store_mem_state+0x178/0x190
[c007d9483ce0] [c061ea34] dev_attr_store+0x34/0x60
[c007d9483d00] [c03bdd10] sysfs_kf_write+0x60/0xa0
[c007d9483d20] [c03bcaac] kernfs_fop_write+0x16c/0x240
[c007d9483d70] [c0314cf4] __vfs_write+0x34/0x70
[c007d9483d90] [c031673c] vfs_write+0xcc/0x230
[c007d9483de0] [c0318410] SyS_write+0x60/0x110
[c007d9483e30] [c000b860] system_call+0x58/0x6c
Instruction dump:
e90a0030 88ff0007 7fa94000 419e0120 3d005dea e8df0028 e8bf0020 7fe4fb78
6108dbee 7d435378 790807c6 6508f000  f8a6 7d094378 61080100
---[ end trace 23e3dda3fe0a58bd ]--

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

Title:
  Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run
  with 16Gb hugepages configured

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

Bug description:
  Issue:

  Call traces occurs when memory-hotplug script is run with 16Gb
  hugepages configured.

  Environment:
  ppc64le PowerVM Lpar

  root@ltctuleta-lp1:~# uname -r
  4.4.0-34-generic

  root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge
  AnonHugePages: 0 kB
  HugePages_Total:   2
  HugePages_Free:2
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB

  root@ltctuleta-lp1:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:85G 32G 52G 16M193M 
52G
  Swap:   43G  0B 43G

  Steps to reproduce:
  1 - Download kernel source and enter to the directory- 
tools/testing/selftests/memory-hotplug/
  2 - Run  mem-on-off-test.sh script in it.

  System gives call traces like:

  offline_memory_expect_success 639: unexpected fail
  online-offline 668
  [   57.552964] Unable to handle kernel paging request for data at address 
0x0028
  [   57.552977] Faulting instruction address: 0xc029bc04
  [   57.552987] Oops: Kernel access of bad area, sig: 11 [#1]
  [   57.552992] SMP NR_CPUS=2048 NUMA pSeries
  [   57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc 
autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel 
rtc_generic mdio libcrc32c
  [   57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not

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

2018-01-23 Thread Ubuntu Kernel Bot 
This change was made by a bot.

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

** Tags added: zesty

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

Title:
  error loading realtime clock since upgrading to 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (originally asked over at askubuntu.com, but is still unresolved:
  https://askubuntu.com/questions/971349/problem-with-real-time-clock-
  since-upgrading-to-ubuntu-17-10)

  I recently upgraded from Ubuntu 17.04 to Ubuntu 17.10 using the
  software update process. The update completed without any errors, and
  Ubuntu 17.10 is now running without any major issues.

  However, I was running a script previously that uses rtcwake which has
  since stopped working. The script automatically hibernates my laptop
  after a set period of time in sleep mode, and was working perfectly in
  Ubuntu 17.04.

  In the process of troubleshooting, I discovered that the problem was
  with rtcwake which is complaining about /dev/rtc0 missing.

  Here is output from a sample rtcwake command:

  peter@haven:~$ rtcwake -m no -s 1300
  rtcwake: assuming RTC uses UTC ...
  rtcwake: /dev/rtc0: unable to find device: No such file or directory

  I verified that in fact, that directory is missing. Since this was
  working prior to the upgrade, I have to assume that it was there
  previously, but I don't know for sure.

  In researching the error, I found some suggestions to get further
  information with timedatectl and hwclock, so here are the results from
  those commands as well.

  Output of timedatectl:

  peter@haven:~$ timedatectl
Local time: Fri 2017-10-27 19:06:26 EDT
Universal time: Fri 2017-10-27 23:06:26 UTC
  RTC time: n/a
 Time zone: America/New_York (EDT, -0400)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  Output of hwclock --debug:

  peter@haven:~$ sudo hwclock --debug
  [sudo] password for peter: 
  hwclock from util-linux 2.30.1
  Trying to open: /dev/rtc0
  Trying to open: /dev/rtc
  Trying to open: /dev/misc/rtc
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  UPDATE

  When I boot with my old kernel, 4.10.0-37-generic the real-time clock
  works fine.

  I get the following RTC messages in dmesg when I boot the
  4.13.0-16-generic kernel:

  peter@haven:~$ dmesg | grep -i rtc
  [0.089393] RTC time: 17:03:55, date: 11/01/17
  [1.238784] rtc_cmos 00:01: RTC can wake from S4
  [1.238794] rtc_cmos: probe of 00:01 failed with error -16
  [1.295459] hctosys: unable to open rtc device (rtc0)

  UPDATE #2

  Well, I was starting to believe that I had a hardware issue, since
  discovering I was unable to save changes to my BIOS and could not boot
  from USB. As it turns out, my laptop was bitten by this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 causing
  my BIOS to be locked in a read-only state.

  Once I resolved the BIOS issue, and fixed the USB boot problem, I did
  a live boot of Ubuntu 17.10. The issue with my real time clock still
  exists under this clean boot scenario, yet when I boot other distros,
  like Linux Mint 18.3 and the real time clock works fine. I feel this
  definitely has something to do with the Ubuntu install, perhaps even a
  kernel bug.

  UPDATE #3

  More evidence to suggest this is a kernel bug: I live-booted a copy of
  Antergos Linux, which was using the Arch kernel 4.14.12-1-ARCH and it
  exhibited the same problem with the real time clock as Ubuntu 17.10.
  In addition, I confirmed that the Linux Mint version I booted earlier
  (see Update #2) was on the Ubuntu kernel 4.10.0-38-generic.

  So, I suspect that sometime between kernels 4.10 and 4.13 this bug was 
introduced.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1832 F pulseaudio
   /dev/snd/controlC1:  peter  1832 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=a602efe1-467d-4ac4-806f-1b931c91cdad
  InstallationDate: Installed on 2017-04-05 (292 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20354
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=fa5454aa-9072-475d-b515-acd51a6166cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )

2018-01-23 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  In Progress
Status in libatasmart source package in Trusty:
  Confirmed
Status in libatasmart source package in Xenial:
  Confirmed
Status in libatasmart source package in Yakkety:
  Confirmed

Bug description:
  Hello, here's my system info

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

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

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

  1   2   >