[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2019-06-20 Thread Brian Murray
** Changed in: lvm2 (Ubuntu Eoan)
Milestone: ubuntu-16.03 => None

** Changed in: lvm2 (Ubuntu Eoan)
 Assignee: Andy Whitcroft (apw) => (unassigned)

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New
Status in lvm2 source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in lvm2 source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in lvm2 source package in Disco:
  New
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  In Progress
Status in lvm2 package in Debian:
  Unknown

Bug description:
  After upgrading to Wily, raid1 LVs don't activate during the initrd
  phase. Since the root LV is also RAID1-mirrored, the system doesn't
  boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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


[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2019-06-20 Thread Brian Murray
** Tags removed: rls-bb-incoming

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  New
Status in lvm2 source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in lvm2 source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in lvm2 source package in Disco:
  New
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  In Progress
Status in lvm2 package in Debian:
  Unknown

Bug description:
  After upgrading to Wily, raid1 LVs don't activate during the initrd
  phase. Since the root LV is also RAID1-mirrored, the system doesn't
  boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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


[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2019-06-18 Thread Brian Murray
** Tags added: rls-bb-incoming

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  In Progress
Status in lvm2 package in Debian:
  Unknown

Bug description:
  After upgrading to Wily, raid1 LVs don't activate during the initrd
  phase. Since the root LV is also RAID1-mirrored, the system doesn't
  boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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


[Kernel-packages] [Bug 1828187] Please test proposed package

2019-06-18 Thread Brian Murray
Hello bugproxy, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  ibm,dynamic-memory property not found while loading kexec kernel
  (4.18.0-18-generic)

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

Bug description:
  For SRU:

  [Impact]

   * The ibm,dynamic-memory-v2 device tree property replaced the
  original ibm,dynamic-memory property. Since kexec-tools doesn't know
  to look for the "-v2" property yet, it fails to successfully parse the
  node using the new "-v2" property.

   * These changes enable the new "-v2" property to be successfully
  parsed from the node.

  [Test Case]

   * Load panic kernel or regular kernel with kexec command:

  kdump-config unload; kdump-config load

  OR

  kexec -l --append="`cat /proc/cmdline`"
  --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`

  * Expected result: kexec loads without any warning/error messages

  [Testing]

  These changes were tested by Hari with a positive result on a 4.18
  kernel for ppc64el.

  [Regression Potential]

  * Low. 
  * These changes exist in 'kexec-tools' for disco and onwards (these kernels 
are all >= 4.16 where the -v2 property was enabled). 
  * The Bionic edge and Cosmic kernels have support for the -v2 property since 
they are also >= 4.16.
  * The regular 4.15 Bionic kernel is the more interesting of the bunch in 
terms of regression potential since 4.15 is too early to have the -v2 property 
enabled. The changes introduced by this patch appear to only attempt "-v2" 
parsing if it was unable to parse the "-v1" node. The absence of the v1 node 
implies that the device tree is using the "v2" property. Since the "-v2" option 
is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" 
parsing will certainly fail, and the code throws the same error condition is it 
did before the patch was applied anyway.

  Original bug description below.
  ---

  == Comment: #0 - Hari Krishna Bathini  - 2019-05-07 
13:37:51 ==
  ---Problem Description---
  On 4.18.0-18-generic kernel, kexec load command throws below traces:

  ---

  Regular kexec load:

  root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" 
--initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`
  /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No 
such file or directory
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic 
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
  root@ubuntu:~#
  ---

  KDump kernel load:

  root@ubuntu:~# kdump-config unload
   * unloaded kdump kernel
  root@ubuntu:~# kdump-config load
   * Creating symlink /var/lib/kdump/vmlinuz
   * Creating symlink /var/lib/kdump/initrd.img
  /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No 
such file or directory
  /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No 
such file or directory
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic 
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 
systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb 
elfcorehdr=158912K
   * loaded kdump kernel
  root@ubuntu:~#
  ---

  Contact Information = hbath...@in.ibm.com

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

  ---Additional Hardware Info---
  na

  Machine Type = na

  

[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)

2019-06-18 Thread Brian Murray
Hello bugproxy, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: kexec-tools (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: kexec-tools (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  ibm,dynamic-memory property not found while loading kexec kernel
  (4.18.0-18-generic)

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

Bug description:
  For SRU:

  [Impact]

   * The ibm,dynamic-memory-v2 device tree property replaced the
  original ibm,dynamic-memory property. Since kexec-tools doesn't know
  to look for the "-v2" property yet, it fails to successfully parse the
  node using the new "-v2" property.

   * These changes enable the new "-v2" property to be successfully
  parsed from the node.

  [Test Case]

   * Load panic kernel or regular kernel with kexec command:

  kdump-config unload; kdump-config load

  OR

  kexec -l --append="`cat /proc/cmdline`"
  --initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`

  * Expected result: kexec loads without any warning/error messages

  [Testing]

  These changes were tested by Hari with a positive result on a 4.18
  kernel for ppc64el.

  [Regression Potential]

  * Low. 
  * These changes exist in 'kexec-tools' for disco and onwards (these kernels 
are all >= 4.16 where the -v2 property was enabled). 
  * The Bionic edge and Cosmic kernels have support for the -v2 property since 
they are also >= 4.16.
  * The regular 4.15 Bionic kernel is the more interesting of the bunch in 
terms of regression potential since 4.15 is too early to have the -v2 property 
enabled. The changes introduced by this patch appear to only attempt "-v2" 
parsing if it was unable to parse the "-v1" node. The absence of the v1 node 
implies that the device tree is using the "v2" property. Since the "-v2" option 
is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2" 
parsing will certainly fail, and the code throws the same error condition is it 
did before the patch was applied anyway.

  Original bug description below.
  ---

  == Comment: #0 - Hari Krishna Bathini  - 2019-05-07 
13:37:51 ==
  ---Problem Description---
  On 4.18.0-18-generic kernel, kexec load command throws below traces:

  ---

  Regular kexec load:

  root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`" 
--initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`
  /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No 
such file or directory
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic 
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
  root@ubuntu:~#
  ---

  KDump kernel load:

  root@ubuntu:~# kdump-config unload
   * unloaded kdump kernel
  root@ubuntu:~# kdump-config load
   * Creating symlink /var/lib/kdump/vmlinuz
   * Creating symlink /var/lib/kdump/initrd.img
  /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No 
such file or directory
  /proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No 
such file or directory
  Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic 
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1 
systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb 
elfcorehdr=158912K
   * loaded kdump 

[Kernel-packages] [Bug 1813463] Re: no bluetooth intel ac 9260

2019-06-12 Thread Brian Murray
** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  no bluetooth intel ac 9260

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi All

  Using a laptop with the intel AC 9260 wireless card that also has Bluetooth 
5.0.
  Booting either ubuntu 18.04 or 18.10 with kernel 4.18.* through to 4.20.* the 
bluetooth is not detected and can't be switched on.

  hciconfig -a
  Produces no result

  $ bluetoothctl
  Agent registered
  [bluetooth]# show
  No default controller available
  [bluetooth]# devices
  No default controller available
  [bluetooth]#

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

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


[Kernel-packages] [Bug 1832435] Re: Lenovo miix 510 wifi adapter cannot be turned on

2019-06-12 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Lenovo miix 510 wifi adapter cannot be turned on

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This problem appears when you first install ubuntu 18.04, 18.10, and
  19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions
  of ubuntu.  After installation or update to a newer versio of ubuntu
  the network adaptor is set to off and cannot be turned on. I believe
  this is because of a non-existent or faulty driver for the intel 8260
  wifi adapter. It also could be that the driver is waiting for physical
  or keyboard switch to turn on the adapter. However, no such switch
  exists in this laptop model.

  The problem can be resolved by adding "blacklist ideapad_laptop" to
  the configuration file

  /etc/modprobe.d/blacklist.conf

  (this is for ubuntu 19.04. The filename and location are different for
  18.04 and 18.10)

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

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


[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-10 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  systemd-networkd:   Lost carrier e1000

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just installed a fresh installation of ubuntu 19 on our server and
  we're having a lot of carrier-lost erros.

  There is no really good indicaton why this is hapening.

  Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO 
to off.
  removed netplan, switched to systemd-networkd and added 
configurewithoutcarrier to true, the option ignorecarrierlost is not accepted 
by systemd.

  Description:Ubuntu 19.04
  Release:19.04

  
  Kernel Log

  Jun  8 12:11:17 mc2 kernel: [30304.199050] [ cut here 
]
  Jun  8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): 
transmit queue 0 timed out
  Jun  8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at 
net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul 
  crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof 
intel_pch_thermal mac_hid acpi_pad ip6t_REJE
  CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
sch_fq_codel xt_conntrack ip6
  table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter ip_
  tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath 
linear raid1 e1000e
   nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake 
pinctrl_intel
  Jun  8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not 
tainted 5.0.0-16-generic #17-Ubuntu
  Jun  8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology 
Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
  Jun  8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230
  Jun  8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 
ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 
89 c2 e8 71 f1 79 ff
   <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48
  Jun  8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 
00010286
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RAX:  RBX: 
 RCX: 0006
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 
0096 RDI: 93adff216440
  Jun  8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 
0001 R09: 0c61
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: 
 R12: 0001
  Jun  8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 
93adec4804c0 R15: 93adeca74080
  Jun  8 12:11:17 mc2 kernel: [30304.199086] FS:  () 
GS:93adff20() knlGS:
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun  8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 
00043920e003 CR4: 003606e0
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR0:  DR1: 
 DR2: 
  Jun  8 12:11:17 mc2 kernel: [30304.199087] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Jun  8 12:11:17 mc2 kernel: [30304.199087] Call Trace:
  Jun  8 12:11:17 mc2 kernel: [30304.199088]  
  Jun  8 12:11:17 mc2 kernel: [30304.199090]  ? pfifo_fast_enqueue+0x120/0x120
  Jun  8 12:11:17 mc2 kernel: [30304.199091]  call_timer_fn+0x30/0x130
  Jun  8 12:11:17 mc2 kernel: [30304.199092]  run_timer_softirq+0x3e4/0x420
  Jun  8 12:11:17 mc2 kernel: [30304.199093]  ? ktime_get+0x3c/0xa0
  Jun  8 12:11:17 mc2 kernel: [30304.199095]  ? lapic_next_deadline+0x26/0x30
  Jun  8 12:11:17 mc2 kernel: [30304.199096]  ? 
clockevents_program_event+0x93/0xf0
  Jun  8 12:11:17 mc2 kernel: [30304.199097]  __do_softirq+0xdc/0x2f3
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  irq_exit+0xc0/0xd0
  Jun  8 12:11:17 mc2 kernel: [30304.199099]  
smp_apic_timer_interrupt+0x79/0x140
  Jun  8 12:11:17 mc2 kernel: [30304.199100]  apic_timer_interrupt+0xf/0x20
  Jun  8 12:11:17 mc2 kernel: [30304.199101]  
  Jun  8 12:11:17 mc2 kernel: [30304.199102] RIP: 
0010:cpuidle_enter_state+0xbd/0x450
  Jun  8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 
00 74 17 9c 58 0f 1f 44 

[Kernel-packages] [Bug 1817321] Please test proposed package

2019-06-04 Thread Brian Murray
Hello Mauricio, or anyone else affected,

Accepted hw-detect into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/hw-
detect/1.117ubuntu6.18.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  In Progress
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  In Progress
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  In Progress
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
    

[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-06-04 Thread Brian Murray
Hello Mauricio, or anyone else affected,

Accepted hw-detect into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/hw-
detect/1.117ubuntu6.18.10.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: hw-detect (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

** Changed in: hw-detect (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  In Progress
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  In Progress
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  In Progress
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
   

[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-06-04 Thread Brian Murray
Hello Mauricio, or anyone else affected,

Accepted hw-detect into disco-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/hw-
detect/1.117ubuntu6.19.04.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: hw-detect (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  In Progress
Status in hw-detect source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  In Progress
Status in debian-installer source package in Cosmic:
  In Progress
Status in hw-detect source package in Cosmic:
  In Progress
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  In Progress
Status in debian-installer source package in Disco:
  In Progress
Status in hw-detect source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  In Progress
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled 

[Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors

2019-05-24 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  System freezes repeatedly for several seconds; wifi driver related
  errors

Status in linux package in Ubuntu:
  New

Bug description:
  I updated my system about a month ago (Fri 26 April 2019). This was
  the first update in several weeks and installed fresh versions of a
  whole truck load of applications including a kernel update. Since this
  latest bunch of updates the system freezes for a few seconds at
  regular intervals. Not fatal, but very annoying.

  Output from "journalctl -f" shows the following errors occurring at
  the same time as these freezes:

  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive 
scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: 
-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw 
scan: -110

  Corresponding lines in /var/log/syslog:

  May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record 
for fe80::424:c75b:2a2d:52e2 on wlp3s0.*.
  May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for 
fe80::424:c75b:2a2d:52e2 on wlp3s0.
  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: 
failed to receive scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: 
failed to stop scan: -110
  May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: 
failed to start hw scan: -110

  I do note the interval between the avahi-daemon entry and the
  subsequent errors related to the wireless network interface, but the
  former precede the latter consistently in syslog, suggesting they may
  be related, which is why I'm including it in this report.

  The freezes last a few seconds. Keyboard input is preserved at this
  time and typed input appears after the freeze is resolved. Mouse
  cursor continues to move during freezes but mouse clicks are only
  processed after the freeze is resolved, i.e. the result of the mouse
  click is suspended (e.g. buffered) until the system becomes responsive
  again. For example, clicking on a window during the freeze will focus
  that window after the freeze has been resolved.

  The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk:

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter [168c:0042] (rev 31)

  Output of lsb_release -rd:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  Output of uname -a:
  Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  As already said, this is a new issue that has began occurring only
  after the recent batch of updates that included a kernel update. I
  reported the bug (maybe in the wrong place) but so far I have received
  no response. I've lived with this for a month or so hoping that
  further updates would fix the problem but it still persists.
  Installing the latest firmware update (14 Mar 2019) has no effect. No
  other changes were made to either hardware or OS configuration.

  Logfile snippets attached.

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

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


[Kernel-packages] [Bug 1828906] Re: upgrade to Linux 4.15.0-48-generic crashes display on lenovo G500

2019-05-21 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  upgrade to Linux 4.15.0-48-generic crashes display on lenovo G500

Status in linux package in Ubuntu:
  New

Bug description:
  Last week my Lenovo G500 laptop running ubuntu 18.04 reported an
  available system update of about 180 MBs, which included a kernel
  version update. I installed it and following the reboot, the display
  hung with a purple screen with bands of random colored pixels across
  the screen.

  If I reboot and hold down SHIFT to get to GRUB, it presents the
  following choices under Advanced Options:

Ubuntu, with Linux 4.15.0-48-generic
Ubuntu, with Linux 4.15.0-48-generic (recovery mode)
Ubuntu, with Linux 4.15.0-47-generic
Ubuntu, with Linux 4.15.0-47-generic (recovery mode)

  If I select 4.15.0-48-generic, I get the display hang problem
  described above or other forms of display misbehavior (sometimes it
  flashes continuously, sometimes it just hangs at a black screen, its
  not consistent).

  If I select 4.15.0-47-generic, it boots up just fine to a completely
  usable desktop. Every time.

  I've tried running boot-repair. It reported that it had repaired GRUB,
  but the problem persists. So I don't think its a boot parameters
  problem. I conclude that the problem has something to do with the
  display driver in 4.15.0-48-generic that was not present in
  4.15.0-47-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.31
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 18:11:02 2019
  InstallationDate: Installed on 2019-04-18 (25 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2019-05-13 16:34:52.461061
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2019-05-13 16:35:07.526926

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

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


[Kernel-packages] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind

2019-05-16 Thread Brian Murray
** Changed in: nplan (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in nplan source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in nplan source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  netplan-configured systems with mwifiex interfaces crash if netplan attempts 
to unbind/bind the interface.

  [Test case]
  1) Run 'netplan apply' on a system with mwifiex_pci driver.

  The system should not crash, and the mwifiex interface should remain
  untouched.

  [Regression potential]
  Interfaces other than those affected by unbind/bind crashes or failures 
should still be unbound when 'netplan apply' is run. This affects most wireless 
interfaces, with the notable exception of mwifiex and brcmfmac. Failure to 
apply netplan configuration for a legitimate mwifiex device (wireless 
connection driven by NetworkManager renderer using netplan) would also 
constitute a regression.

  [Original bug report]
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind

  Keep doing the bind/unbind actions, it would crash very soon.

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

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


[Kernel-packages] [Bug 1829340] Re: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0

2019-05-16 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01)
  subsystem 103c:17d0

Status in linux package in Ubuntu:
  New

Bug description:
  Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network 
Connection (rev 0)
  PCIID: 8086:10fb subsystem 103c:17d0

  I have tried to install Ubuntu 16.04 with default kernel v4.4 and backported 
kernel from 18.04 v4.15. PXE boot process works well till the moment when the 
installer tries to load the ixgbe driver for NIC. The driver fails to 
initialize NIC with the following error messages in the syslog: 
  ixgbe: Intel(r) 10 Gigabit PCI Express Network Driver - version 5.1.0-k
  ixgne: Copyright (c) 1999-20016 Intel Corporation
  ixgbe: probe of :03:00.0 failed with error -5
  ixgbe: probe of :03:00.1 failed with error -5

  I have used the most recent initrd and kernel from 
  
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/hwe-netboot/ubuntu-installer/amd64/

  file linux initrd.gz
  linux: Linux/x86 Kernel, Setup Version 0x20d, bzImage, Version 4.15.0, 
Version 4.15.0-45, RO-rootFS, swap_dev 0x7, Normal VGA
  initrd.gz: gzip compressed data, was "initrd", from Unix, last modified: Wed 
Feb 20 06:36:36 2019, max compression

  
  Also I'd like to say that 

  * the same issue with ixgbe 4.2.1-k if I use the installer of Ubuntu 16.04 
with kernel v4.4
  * ixgbe v4.2.1-k from SLES12SP2 works correctly.

  #this is SLES12 host with more info about ixgbe from SLES12.
  :~ # modinfo ixgbe 
  filename:   
/lib/modules/4.4.90-92.50-default/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.2.1-k   

  license:GPL   

  description:Intel(R) 10 Gigabit PCI Express Network Driver

  author: Intel Corporation,  

  srcversion: F8D1434936208D466C73062

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

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


[Kernel-packages] [Bug 1829095] Re: Keyborad backligt does not work

2019-05-15 Thread Brian Murray
** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  Keyborad backligt does not work

Status in linux package in Ubuntu:
  New

Bug description:
  I have a dell XPS14 (L421X).  In releases 18.04 and lower the keyboard
  back light used to work.  However in 18.10 and 19.04 it does not

  The dell_laptop model is loaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-desktop 1.431
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 15 11:44:51 2019
  InstallationDate: Installed on 2019-04-23 (21 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1828712] Re: I/O errors when trying to loop mount an image

2019-05-13 Thread Brian Murray
apport-cli contains an option for save the report from another machine.
apport-cli --help says:

  --save=PATH   In bug filing mode, save the collected information
into a file instead of reporting it. This file can
then be reported later on from a different machine.

and:

  -c PATH, --crash-file=PATH
Report the crash from given .apport or .crash file
instead of the pending ones in /var/crash. (Implied if
file is given as only argument.)

However, this doesn't work with apport-collect but if the Ubuntu Kernel
Bot still wants this you could open a new bug report using --save and
the --crash-file.

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

Title:
  I/O errors when trying to loop mount an image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Command

sudo mount -t vfat flop1 /mnt/flop1

  fails. The image is readable but the log shows many I/O errors such as

  May 12 07:57:24 us64a kernel: [69801.335823] print_req_error: I/O error, dev 
loop0, sector 0
  May 12 07:57:24 us64a kernel: [69801.337707] print_req_error: I/O error, dev 
loop0, sector 0
  May 12 07:57:24 us64a kernel: [69801.339521] FAT-fs (loop0): unable to read 
boot sector
  May 12 07:57:24 us64a kernel: [69801.342063] print_req_error: I/O error, dev 
loop0, sector 0
  May 12 07:57:24 us64a kernel: [69801.343891] Buffer I/O error on dev loop0, 
logical block 0, async page read
  May 12 07:57:24 us64a kernel: [69801.345974] print_req_error: I/O error, dev 
loop0, sector 1
  May 12 07:57:24 us64a kernel: [69801.347832] Buffer I/O error on dev loop0, 
logical block 1, async page read
  May 12 07:57:24 us64a kernel: [69801.349928] print_req_error: I/O error, dev 
loop0, sector 2
  May 12 07:57:24 us64a kernel: [69801.351818] Buffer I/O error on dev loop0, 
logical block 2, async page read
  May 12 07:57:24 us64a kernel: [69801.356103] print_req_error: I/O error, dev 
loop0, sector 3
  May 12 07:57:24 us64a kernel: [69801.356109] Buffer I/O error on dev loop0, 
logical block 3, async page read
  May 12 07:57:24 us64a kernel: [69801.356117] print_req_error: I/O error, dev 
loop0, sector 4
  May 12 07:57:24 us64a kernel: [69801.356119] Buffer I/O error on dev loop0, 
logical block 4, async page read
  May 12 07:57:24 us64a kernel: [69801.356122] print_req_error: I/O error, dev 
loop0, sector 5
  May 12 07:57:24 us64a kernel: [69801.356125] Buffer I/O error on dev loop0, 
logical block 5, async page read
  May 12 07:57:24 us64a kernel: [69801.356128] print_req_error: I/O error, dev 
loop0, sector 6
  May 12 07:57:24 us64a kernel: [69801.356130] Buffer I/O error on dev loop0, 
logical block 6, async page read
  May 12 07:57:24 us64a kernel: [69801.356134] print_req_error: I/O error, dev 
loop0, sector 7
  May 12 07:57:24 us64a kernel: [69801.356136] Buffer I/O error on dev loop0, 
logical block 7, async page read
  May 12 07:57:24 us64a kernel: [69801.356260] Buffer I/O error on dev loop0, 
logical block 0, async page read
  May 12 07:57:24 us64a kernel: [69801.356263] Buffer I/O error on dev loop0, 
logical block 1, async page read

  The command, understandably, reports "can't read superblock on
  /dev/loop0". The problem happens even on newly created images. Here's
  a sample set of commands and responses:

  $ mkfs.msdos -C flop1 1440
  $ ls -l
  -rwxrwxrwx 1 root root 1474560 May 10 18:49 flop1
  $ hd flop1
  <--- output looks reasonable including 55 aa and two FATs --->
  $ sudo mkdir /mnt/flop1
  $ sudo mount -o loop flop1 /mnt/flop1
  mount: /mnt/flop1: can't read superblock on /dev/loop0.
  $ losetup -f
  /dev/loop0
  $

  I see plenty of reports of similar on different websites but without
  resolution, including one on Launchpad but where the OP stopped
  responding so it did not get resolved. I don't know when this problem
  started to occur on this machine.

  If it's relevant, this is running under VirtualBox which reports
  itself as Version 5.2.26 r128414 (Qt5.6.2) with their 'host
  extensions' enabled. However, mounting a floppy image previously
  worked on this virtual machine.

  I have rebooted with /forcefsck to check the root (and only)
  filesystem. I have upgraded to the latest LTS Ubuntu, as below, but
  the problem persists.

  System info:

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  Linux us64a 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5
  10:22:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  The machine is command-line only, i.e. no windowing.

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

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

[Kernel-packages] [Bug 1821823] Update Released

2019-04-30 Thread Brian Murray
The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  No wireless networks displayed for broadcom BCM43142

Status in dkms package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid
Status in dkms source package in Disco:
  Fix Released

Bug description:
  [Impact]

  The dkms version available in disco regressed in behavior in
  comparison to earlier series, causing `dkms uninstall` removing the
  module from the built tree instead of only uninstalling it. Per the
  dkms manpage, an uninstall operation should leave the module in the
  'built' state, while currently it ends up only in the 'added' state.

  This breaks our current shim-signed logic, since on postinst we're
  uninstalling every dkms module, checking if we uninstalled it
  correctly by making sure it's in the 'built' state and then signing it
  if everything is ok. And this is now broken.

  This seemed to have been introduced unintentionally as the manpage still 
notes for `dkms uninstall`:
  "Uninstalls an installed module/module-version combo from the kernel/arch 
passed in the -k option, or the current kernel if the -k option was not passed 
upon. After uninstall completion, the driver will be left in the built state.
  To completely remove a driver, the remove action should be utilized."

  The bug has been made visible with the bcmwl-kernel-source driver,
  which, if installed before shim-signed, will then become uninstalled
  and not reinstalled again (because of the failed status check before
  signing).

  [Test Case]

  An easy way of checking if the uninstall logic has been reverted:

   1. On a disco system, install the dkms and bcmwl-kernel-source packages 
(-proposed disabled).
   2. Check the version of the module installed `dkms status`.
   3. Once the installation completes, uninstall the bcmwl dkms module from the 
system:
   `dkms uninstall bcmwl/`
   4. Checks that the status is not reported as 'built' (should be something 
like 'added' only):
   `dkms status bcmwl`
   5. Enable disco-proposed and upgrade dkms.
   6. Re-install the bcmwl-kernel-source package.
   7. Once again uninstall the bcmwl dkms module:
   `dkms uninstall bcmwl/`
   8. Check the status and notice that it is now reported as 'built':
   `dkms status bcmwl`

  Another way would be checking on a secureboot-enabled system that has
  Broadcom wireless installing the -proposed dkms, then bcmwl-kernel-
  source and finally shim-signed (reinstalling if necessary). This
  operation should result in the broadcom dkms module still being
  installed and active. But this test should be counted as an optional
  'additional test'.

  [Regression Potential]

  Since this does change the dkms uninstall behavior, there is always
  some risk involved. One of the potential regressions could be related
  to kernel uninstallation, as we are reverting parts of the kernel
  prerm scripts along with the revert - but the risk should be low as
  we're actually reverting to the state we had in all series prior to
  disco. In overall the uninstall command of dkms might have regressed
  its behavior in case some other place started assuming the removals of
  modules from the built directory, but seeing the disco diff it's
  highly improbable.

  [Original Description]

  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.

  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  IwConfig:
   lono wireless extensions.

   enp3s0no 

[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142

2019-04-16 Thread Brian Murray
The log file wasn't actually attached, could you find it again and add
it?

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

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

Title:
  No wireless networks displayed for broadcom BCM43142

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

Bug description:
  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.

  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: noSourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142

2019-04-02 Thread Brian Murray
Could you add the ubiquity log file to the bug report or try and the
beta iso image and then include the ubiquity log file?

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

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

Title:
  No wireless networks displayed for broadcom BCM43142

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

Bug description:
  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.

  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: noSourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142

2019-03-29 Thread Brian Murray
** Description changed:

  For 19.04 UB did a minimal install.  I selected the ubiquity proprietary
  option and expected the broadcom driver to be found and installed.
  
- On reboot I could not see and wireless networks.  I went to the
+ On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.
  
  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 19.04
+ ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dad1060 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  IwConfig:
-  lono wireless extensions.
-  
-  enp3s0no wireless extensions.
+  lono wireless extensions.
+ 
+  enp3s0no wireless extensions.
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
-  Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
-  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
+  Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
+  Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-7-generic N/A
-  linux-backports-modules-5.0.0-7-generic  N/A
-  linux-firmware   1.178
+  linux-restricted-modules-5.0.0-7-generic N/A
+  linux-backports-modules-5.0.0-7-generic  N/A
+  linux-firmware   1.178
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
- SourcePackage: linux
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: noSourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
-  
+ 
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

** Tags added: rls-dd-incoming

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

Title:
  No wireless networks displayed for broadcom BCM43142

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

Bug description:
  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see any wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.

  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.

  ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  

[Kernel-packages] [Bug 1822044] Re: Laptop freezes after installation is finished when pressing "Restart Now"

2019-03-28 Thread Brian Murray
Additionally, if you choose to reboot from the live environment without
installing what happens?

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

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

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

** Changed in: ubiquity (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/1822044

Title:
  Laptop freezes after installation is finished when pressing "Restart
  Now"

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

Bug description:
  As stated in lp:1822026, the Dell Precision 7530 I'm using is using
  nouveau graphics drivers by default when starting a live session, and
  this driver is prone to errors.

  One of the most annoying for a new user is the following:

  1. Boot into 19.04 live session
  2. Launch "Install Ubuntu 19.04" and go through the installation steps
  3. Once the install is done, the "Installation Complete" dialog is shown with 
two options: [Continue Testing][Restart Now]
  4. Press [Restart Now]

  Expected behaviour:

  4. The device restarts and boots into freshly installed Ubuntu 19.04.

  Actual behaviour:

  4. The device freezes and even the keyboard combination SysRq+REISUB
  doesn't do anything. User has to force shutdown the device by pressing
  Power button for a few seconds, remember to remove the USB drive, then
  manually start the device.

  All the hardware-related information is available in the sosreport
  attachment in lp:1822026:
  
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822026/+attachment/5249977/+files
  /sosreport-ubuntu-20190328033617.tar.xz

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

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


[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

2019-03-22 Thread Brian Murray
** Tags added: rls-ee-incoming

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

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

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


[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

2019-03-05 Thread Brian Murray
Hello Dean, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

** Changed in: apt (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Trusty:
  Fix Committed
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-hwe source package in Trusty:
  New
Status in apt source package in Xenial:
  Fix Committed
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  Fix Released
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  Fix Released
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Triaged
Status in linux-meta-hwe source package in Disco:
  Triaged

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully 

[Kernel-packages] [Bug 1787460] Please test proposed package

2019-03-05 Thread Brian Murray
Hello Dean, or anyone else affected,

Accepted apt into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.21 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Trusty:
  Fix Committed
Status in linux-meta source package in Trusty:
  New
Status in linux-meta-hwe source package in Trusty:
  New
Status in apt source package in Xenial:
  Fix Committed
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  Fix Released
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  Fix Released
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Triaged
Status in linux-meta-hwe source package in Disco:
  Triaged

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  

[Kernel-packages] [Bug 1818187] Re: Any USB plugged works slow or even not detected well

2019-03-04 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Any USB plugged works slow or even not detected well

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Everytime i plug a USB device like mouse or joystick, they move super
  slow, or arent detected when i dmesg i got the following:

  
  [  768.390547] hid-generic 0003:046D:C52F.0002: can't resubmit intr, 
:00:12.0-2/input1, status -19

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

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


[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-02-27 Thread Brian Murray
** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => Incomplete

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Incomplete
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Incomplete

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 
0x6070 | flow_handler
  Dec 13 11:53:36 james-x1 kernel: [  856.845170] iwlwifi 

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

2019-02-27 Thread Brian Murray
Hello Agustin, or anyone else affected,

Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.2-0ubuntu0.18.04.3 in a few hours, and then
in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  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:
  

[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

2019-02-22 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.

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

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


[Kernel-packages] [Bug 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

2019-02-20 Thread Brian Murray
** Tags added: bugpattern-written

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

Title:
  nvidia-*: nvidia-* kernel module failed to build [error: too many
  arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  NA

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1815733] Re: unnecessary request_queue freeze

2019-02-13 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  unnecessary request_queue freeze

Status in linux package in Ubuntu:
  New

Bug description:
  Hi all,

  In linux-4.15, which is used as hwe-edge in xenial, there's an unexpected 
behavior. It results in latency spikes of generic_make_request() function call.
  How to reproduce:
    1. Run fio:
    fio --name=test --rw=randwrite --direct=1 --filename=/dev/sdt --iodepth=1 
--fsync=1 --ioengine=libaio --write_lat_log loglat
    2. While fio is writing to the device, change nr_requests setting to the 
same value as current:
    echo 256 > /sys/block/sdt/queue/nr_requests
    or: if scheduler is already none:
    echo none > /sys/block/sdt/queue/scheduler
    3. Stop fio and check slat log:
    ...
    3980, 16, 1, 4096
    3999, 17, 1, 4096
    4010, 19, 1, 4096
    4020, 18, 1, 4096
    4045, 10821, 1, 4096
    4054, 25, 1, 4096
    4070, 12, 1, 4096
    4083, 17, 1, 4096
    4094, 16, 1, 4096
    4111, 17, 1, 4096
    ...

  There're a few patches to fix this behavior:
  
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-5.1/block=e5fa81408fb43ebabde65938ef8b20ae879017e7
  
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-5.1/block=fbd72127c975dc8e532ecc73d52f3b1b00935bec

  This behavior affects production systems, because every change uevent
  triggers udev to change settings prior to udev rules. Some software,
  for example arcconf (tool for managing adaptec HBA adapters) triggers
  uevents for every block device. So, every call to arcconf utility
  results in latency spike.

  Could this be backported to 4.15 kernel for xenial/bionic?

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Update Released

2019-02-07 Thread Brian Murray
The verification of the Stable Release Update for upower has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You 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 gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  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/gnome-control-center/+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 1813683] Re: linux-image-4.15.0-44-generic tty login not work

2019-02-05 Thread Brian Murray
*** This bug is a duplicate of bug 1813873 ***
https://bugs.launchpad.net/bugs/1813873

** This bug is no longer a duplicate of bug 1812095
   console login loop after entering username followed by RETURN
** This bug has been marked a duplicate of bug 1813873
   Userspace break as a result of missing patch backport

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

Title:
  linux-image-4.15.0-44-generic tty login not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just updated my ubuntu 18.04 and received the linux-
  image-4.15.0-44-generic.

  After update and reboot the machine, my computer starts normally.

  Seems boot normally

  but when gets to the login screen (I'm not use any kind of graphical
  login manager, boot pure on console/text)

  I just need to press enter (doesn't matter if type my login or not),
  then starts a loop, like if my 'enter' key has some kind of mechanical
  defect.

  Keeps pressing 'enter' until I do a CTRL-C.

  If I press enter key again, starts all over again. Periodically
  pressing 'enter' key in lapse of seconds.

  To prevent, I just had to boot using linux-image-4.15.0-43-generic and
  could login normally.

  What can I provide to you look this? I think it's my first time here
  or one of firsts

  Thanks in advanced.

  Regards

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

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


[Kernel-packages] [Bug 1814439] Re: No login on the text console (tty) more possible (4.15.0-45)

2019-02-05 Thread Brian Murray
*** This bug is a duplicate of bug 1813873 ***
https://bugs.launchpad.net/bugs/1813873

** This bug is no longer a duplicate of bug 1812095
   console login loop after entering username followed by RETURN
** This bug has been marked a duplicate of bug 1813873
   Userspace break as a result of missing patch backport

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

Title:
  No login on the text console (tty) more possible (4.15.0-45)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear Maintainer,

  When updating the kernel from 4.15.0-43 to 4.15.0-45, a fatal error
  occurs when logging in to the text console (multi-user target,
  Runlevel 3). After entering the login name (eg root) plus enter key,
  the cursor immediately moves on from the input prompt for the
  password, i. it sent an empty password for login. This is wrong and
  not correct.

  The cursor moves to enter the password, but jumps immediately. The
  error message "Login incorrect" appears four times. Then the erroneous
  login messages are cleared on the screen and it starts all over again.

  The bug also occurs with kernel 4.18.0-14, which I have installed as a
  trial, affecting at least two kernel versions of it 4.15.0-45 and
  4.18.0-14. The error does not occur if you want to log in as root
  after starting the KDE desktop with the console. So the last working
  kernel is 4.15.0-42.

  The error does not occur if you want to log in as root after starting
  the KDE desktop with the console. Is the error already known neon or
  is there a bug report about it? What can you do that the login with
  the above mentioned kernel versions in the text console works again?

  Distribution: KDE neon User Edition 5.14
  Kernel : 4.15.0-45-generic

  # cat /proc/version_signature
  Ubuntu 4.15.0-45.48-generic 4.15.18

  regards
  Michael

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

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


[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing

2019-02-05 Thread Brian Murray
Hello Mathieu, or anyone else affected,

Accepted shim-signed into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.33.1~16.04.4 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: shim-signed (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: dkms (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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


[Kernel-packages] [Bug 1748983] Please test proposed package

2019-02-05 Thread Brian Murray
Hello Mathieu, or anyone else affected,

Accepted shim-signed into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.33.1~14.04.4 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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


[Kernel-packages] [Bug 1748983] Please test proposed package

2019-02-05 Thread Brian Murray
Hello Mathieu, or anyone else affected,

Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04.10 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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


[Kernel-packages] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load

2019-02-05 Thread Brian Murray
Hello Dan, or anyone else affected,

Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04.10 in
a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: dkms (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All Ubuntu users for whom Secure Boot is enabled.

  [Test cases]
  1) install dkms module (use virtualbox-dkms for example)
  2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 
4.15.0-20-generic).
  3) Verify that the generated module for the new kernel (4.15.0-22-generic in 
this example) is built and signed by verifying that the file in 
/lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature 
appended~:

  $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail 
-n 100
  [...]
  ~Module signature appended~

  4) Reboot
  5) modprobe -v the module.
  It should not respond "Required key not available", and should return with no 
error.
  6) Verify that dkms does not contain PKCS#7 errors.

  
  [Regression potential]
  Possible regressions involve failure to sign and/or be able to load modules 
after updates: failure to sign leading to a module being built but unsigned 
after a new kernel is installed or after a new DKMS module is installed, 
failure to load modules after reboot (usually caused by module being unsigned); 
failure to sign due to missing keys, signature key not being automatically 
slated for enrollment. All these potential regression scenarios present as 
failure to load a DKMS module after a reboot when it should be loaded 
successfully.

  ---

  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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


[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing

2019-02-05 Thread Brian Murray
Hello Mathieu, or anyone else affected,

Accepted dkms into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.6 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: dkms (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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


[Kernel-packages] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load

2019-02-05 Thread Brian Murray
Hello Dan, or anyone else affected,

Accepted dkms into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.6 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: dkms (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Fix Committed
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All Ubuntu users for whom Secure Boot is enabled.

  [Test cases]
  1) install dkms module (use virtualbox-dkms for example)
  2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 
4.15.0-20-generic).
  3) Verify that the generated module for the new kernel (4.15.0-22-generic in 
this example) is built and signed by verifying that the file in 
/lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature 
appended~:

  $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail 
-n 100
  [...]
  ~Module signature appended~

  4) Reboot
  5) modprobe -v the module.
  It should not respond "Required key not available", and should return with no 
error.
  6) Verify that dkms does not contain PKCS#7 errors.

  
  [Regression potential]
  Possible regressions involve failure to sign and/or be able to load modules 
after updates: failure to sign leading to a module being built but unsigned 
after a new kernel is installed or after a new DKMS module is installed, 
failure to load modules after reboot (usually caused by module being unsigned); 
failure to sign due to missing keys, signature key not being automatically 
slated for enrollment. All these potential regression scenarios present as 
failure to load a DKMS module after a reboot when it should be loaded 
successfully.

  ---

  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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


[Kernel-packages] [Bug 1813749] Update Released

2019-02-05 Thread Brian Murray
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon
  4.4.0-1107.112

Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  ADT Testing failed with xenial/linux-snapdragon on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/z/zfs-linux/20190125_170958_97a22@/log.gz

  The debian test script (debian/tests/kernel-smoke-test) doesn't load
  the zfs module causing the tests to fail.

  [Test Case]
  Run autopkgtest of zfs-linux package with xenial/linux-snapdragon kernel.

  Alternatively one can install the zfs-dkms package, download the zfs-linux 
source from version 0.6.5.6-0ubuntu26 and run:
  $ sudo ./debian/tests/kernel-smoke-test

  Making sure the modules are not loaded before running the test
  manually.

  [Fix]
  The solution is to load the zfs module before starting the tests, as done by 
the test script shipped by the packages for Bionic and later series.

  [Regression Potential] 
  Low. The fix changes only the debian test script, so no impact on regular 
users.

  [Other Info]
  The tests were not failing before. I suspect that's being caused by a change 
in the order that the packages are installed before the tests start. With 
previous ADT runs, the zfsutils-linux package was installed after zfs-dkms, so 
that caused systemd to start the zfs-import-scan service, which loaded the 
modules. On these later ADT failed runs, zfs-dkms is installed last, so the 
service is not reloaded and the modules stay unloaded.

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

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-04 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  New

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


[Kernel-packages] [Bug 1814362] Re: jumper EZbook 3 pro touchpad could not click

2019-02-04 Thread Brian Murray
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)

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

Title:
  jumper EZbook 3 pro touchpad could not click

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear everyone.

  I have a jumper EZbook3 pro note pc, and I installed ubuntu-18.04.1.
  I think ubuntu-18.04.1 about work fine, but touchpad could not click.
  My jumper environment ubuntu18.04.1 and windows10home multiboot
  to use rEFInd in UEFI and GPT.

  I use xinput list command
  in Virtual core pinter, SYNA3602:00 0911:5208 Touchpad found,
  and touchpad could tap, 2 finger scroll, 1 finger mouse marker move.
  Why my jumper  touchpad could not click?

  and I set off click on tap at setting up, but nothing to do.

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

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


[Kernel-packages] [Bug 1748983] Missing SRU information

2019-01-31 Thread Brian Murray
Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released

Bug description:
  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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


[Kernel-packages] [Bug 1814015] Re: After upgrade to kernel .44 docking station and external monitors not working

2019-01-30 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  After upgrade to kernel .44 docking station and external monitors not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading the kernel has resulted in displays crashing and external
  displays not working.

  Release: Ubuntu 18.0.4 LTS

  dist-upgrade

  Normal boot is expected - after entering encryption password for hard
  disk get black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 30 20:45:30 2019
  InstallationDate: Installed on 2016-11-10 (811 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (258 days ago)
  VarLogDistupgradeTermlog:

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

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


[Kernel-packages] [Bug 1813763] Re: Screen freeze up after changing display mode to external display only

2019-01-29 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Screen freeze up after changing display mode to external display only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Lenovo ThinkPad X280 with Lenovo USB-C dock
  OS: Ubuntu Desktop 18.04.1 LTS, kernel 4.15.0-44-generic

  == Reproduce steps ==
  1. Connect one screen to Lenovo USB-C dock.
  2. Connect Lenovo ThinkPad X280 to Lenovo USB-C dock.
  3. Boot Ubuntu Linux and login. The external and built-in display will work 
in join display mode.
  4. Press Fn+F7 and select external display only.

  == Expected result ==
  Use the external display to display GUI.

  == Actual result ==
  The built-in display freeze up. Nothing (blank) on the external display.
  System does not respond to keyboard input.
  If there is an external keyboard connected, Num-lock indicator will not 
change after pressing Num-lock key on the external keyboard.

  Other processes are still running. If the Spotify is running, it will keep 
playing the music. Having a script as below will keep writing to a file
  while [ true ]; do
  date >> time-log.log
  sync
  sleep 1
  done

  == Additional information ==
  Not reproducible on Ubuntu 18.04.1 LiveUSB (kernel 4.15.0-29-generic)
  Not reproducible on kernel 4.15.0-43-generic (by selecting the kernel in GRUB)
  Always reproducible on kernel 4.15.0-44-generic
  Not reproducible if the screen is directly connected to the HDMI port on 
ThinkPad X280

  
  On kernel 4.15.0-43-generic, it will generate the following kernel message 
after selecting external display. The external display will work correctly.

  [   80.165447] thunderbolt :04:00.0: control channel starting...
  [   80.165450] thunderbolt :04:00.0: starting TX ring 0
  [   80.165457] thunderbolt :04:00.0: enabling interrupt at register 
0x38200 bit 0 (0x0 -> 0x1)
  [   80.165458] thunderbolt :04:00.0: starting RX ring 0
  [   80.165465] thunderbolt :04:00.0: enabling interrupt at register 
0x38200 bit 12 (0x1 -> 0x1001)

  On kernel 4.15.0-44-generic, it will generate the following kernel message 
after selecting external display. The external display is blank and the 
built-in display will freeze.
  I run command "sleep 60 ; dmesg > dmesg.log" to record the kernel message 
after selecting external display, as the keyboard will become irresponsive.

  [  625.581884] BUG: unable to handle kernel NULL pointer dereference at 
0245
  [  625.581980] IP: intel_ddi_post_disable+0x54/0x170 [i915]
  [  625.581986] PGD 0 P4D 0 
  [  625.581997] Oops:  [#1] SMP PTI
  [  625.582002] Modules linked in: snd_usb_audio snd_usbmidi_lib hid_generic 
usbhid hid cdc_ether usbnet r8152 mii rfcomm ccm xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc cmac snd_hda_codec_hdmi ebtable_filter 
ebtables ip6table_filter ip6_tables devlink iptable_filter bnep 
snd_hda_codec_realtek snd_hda_codec_generic binfmt_misc joydev intel_rapl 
nls_iso8859_1 x86_pkg_temp_thermal arc4 intel_powerclamp coretemp kvm_intel kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_soc_skl 
aesni_intel snd_soc_skl_ipc aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_ext_core intel_cstate snd_soc_sst_dsp iwlmvm snd_soc_sst_ipc
  [  625.582114]  intel_rapl_perf snd_soc_acpi mac80211 snd_soc_core input_leds 
rmi_smbus uvcvideo snd_compress serio_raw ac97_bus intel_wmi_thunderbolt 
wmi_bmof rmi_core snd_pcm_dmaengine iwlwifi videobuf2_vmalloc snd_hda_intel 
snd_seq_midi videobuf2_memops snd_seq_midi_event videobuf2_v4l2 snd_hda_codec 
snd_rawmidi videobuf2_core cfg80211 btusb btrtl snd_hda_core videodev btbcm 
btintel snd_hwdep thinkpad_acpi media bluetooth snd_seq mei_me snd_pcm 
ucsi_acpi snd_seq_device typec_ucsi processor_thermal_device nvram ecdh_generic 
mei shpchp typec intel_soc_dts_iosf intel_pch_thermal snd_timer snd 
int3403_thermal soundcore int340x_thermal_zone acpi_pad int3400_thermal 
acpi_thermal_rel mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 btrfs xor zstd_compress raid6_pq uas usb_storage
  [  625.582229]  i915 i2c_algo_bit drm_kms_helper nvme e1000e syscopyarea 
psmouse sysfillrect sysimgblt ptp fb_sys_fops i2c_i801 pps_core nvme_core drm 
thunderbolt wmi video
  [  625.582266] CPU: 6 PID: 1813 Comm: Xorg Not tainted 4.15.0-44-generic 
#47-Ubuntu
  [  625.582270] Hardware name: LENOVO 20KFS05Q00/20KFS05Q00, BIOS N20ET31W 
(1.16 ) 05/30/2018
  [  625.582344] RIP: 0010:intel_ddi_post_disable+0x54/0x170 [i915]
  [  625.582349] RSP: 0018:9dacc3f97a60 EFLAGS: 00010297
  [  625.582356] RAX: 0007 RBX: 89695408 RCX: 

[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44

2019-01-28 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  External monitors does not work anymore 4.15.0-44

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using a docking station for my laptop. After install the
  4.15.0-44 update my external monitors goes undetected after logging in
  or having the laptop closed.

  I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2)
  Graphics.

  Going back to the 4.15.0-43 version makes it all work fine again.

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

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


[Kernel-packages] [Bug 1813543] Re: Freeze after update from 4.15.0.43 to 4.15.0.44

2019-01-28 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Freeze after update from 4.15.0.43 to 4.15.0.44

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm running Lubuntu 18.04.1 on a Dell Latitude 7490 and the
  Dockingstation TB16.

  After the last system upgrade on Friday, the system is freezing
  directly when I activate the settings in ARandR. It also freeze
  sporadically even if I don't use ARandR.

  Currently I'm running Lubuntu (and writing this issue) with the older
  kernel (4.15.0.43) selected in GRUB without any problems.

  In the attachment is a abstract of the /var/log/apt/history.log.

  I hope someone can help me with this problem.

  Kind regards,
  K1LLUM1N471

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

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


[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2019-01-23 Thread Brian Murray
The real test should be upgrading from Xenial to Bionic and I did that
and the nvidia Driver section was still enabled.

bdmurray@clean-xenial-amd64:/tmp/ubuntu-release-upgrader-n06oth47$ cat 
/etc/X11/xorg.conf
Section "Device"
  Driver "nvidia"
EndSection
bdmurray@clean-xenial-amd64:/tmp/ubuntu-release-upgrader-n06oth47$ grep 
"release-upgrader" /var/log/dist-upgrade/main.log
2019-01-23 08:13:17,917 INFO release-upgrader version '18.04.29' started

The version is incorrectly listed in main.log as DistUpgradeVersion.py
somehow wasn't updated during the build process.

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  Fix Released

Bug description:
  Impact
  --
  Users who have manually configured an xorg.conf file with nvidia enabled as a 
driver will be surprised to have disabled on upgrade to a new release of Ubuntu 
and won't have a graphical display.

  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.

  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf

  When testing the release-upgrader from -proposed you'll need to use
  the -p switch to get the right tarball. Additionally, you'll want to
  add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia
  defaults to True instead of False (line 106) this'll simulate the
  nvidia driver being loaded.

  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.

  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2019-01-23 Thread Brian Murray
I tested this using the ubuntu-release-upgrader from -proposed when
upgrading from Bionic to Cosmic. The nvidia "Driver" line was left in my
/etc/X11/xorg.conf file after the upgrade completed.

bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-1aog5myp$ cat 
/etc/X11/xorg.conf
Section "Device"
Identifier "nvidia"
Driver "nvidia"
EndSection
bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-1aog5myp$ apt-cache 
policy ubuntu-release-upgrader-core | head -n3
ubuntu-release-upgrader-core:
  Installed: 1:18.10.11.3
  Candidate: 1:18.10.11.3
bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-1aog5myp$ grep 
"18.10.11.3" /var/log/dist-upgrade/main.log
2019-01-23 07:29:06,129 INFO release-upgrader version '18.10.11.3' started

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

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  Fix Released

Bug description:
  Impact
  --
  Users who have manually configured an xorg.conf file with nvidia enabled as a 
driver will be surprised to have disabled on upgrade to a new release of Ubuntu 
and won't have a graphical display.

  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.

  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf

  When testing the release-upgrader from -proposed you'll need to use
  the -p switch to get the right tarball. Additionally, you'll want to
  add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia
  defaults to True instead of False (line 106) this'll simulate the
  nvidia driver being loaded.

  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.

  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 

[Kernel-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

2019-01-17 Thread Brian Murray
Setting to v-done for bionic based off comments 11 and 12.

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

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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


[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

2019-01-17 Thread Brian Murray
Could you please add some details about the verification process for
bionic rather than just switching the tags?

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: Fix Committed => Incomplete

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  New

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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


[Kernel-packages] [Bug 1812127] Re: Lfence not serializing

2019-01-17 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Lfence not serializing

Status in linux package in Ubuntu:
  New

Bug description:
  The message appears on screen during computer bootup.  The complete
  message is "Lfence not serializing, switching to generic retpoling".

  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

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

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


[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-15 Thread Brian Murray
Hello Kai-Heng, or anyone else affected,

Accepted thermald into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/thermald/1.7.0-8ubuntu1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: thermald (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

** Tags added: verification-needed-bionic

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Committed
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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


[Kernel-packages] [Bug 1803360] Please test proposed package

2019-01-15 Thread Brian Murray
Hello Kai-Heng, or anyone else affected,

Accepted thermald into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/thermald/1.7.0-5ubuntu2 in a few
hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Committed
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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


[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

2019-01-15 Thread Brian Murray
Hello Dean, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  Fix Committed
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  Fix Committed
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Triaged
Status in linux-meta-hwe source package in Disco:
  Triaged

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: 

[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2019-01-15 Thread Brian Murray
Hello Vern, or anyone else affected,

Accepted ipxe into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ipxe/1.0.0+git-20180124.fbe8c52d-
0ubuntu2.2 in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Fix Released
Status in ipxe-qemu-256k-compat package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in ipxe source package in Trusty:
  Won't Fix
Status in ipxe source package in Xenial:
  Won't Fix
Status in ipxe source package in Bionic:
  Fix Committed
Status in ipxe source package in Cosmic:
  Fix Committed
Status in ipxe source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * VLAN 0 is special (for QoS actually, not a real VLAN)
   * Some components in the stack accidentally strip it, so does ipxe in
     this case.
   * Fix by porting a fix that is carried by other distributions as upstream
     didn't follow the suggestion but it is needed for the use case affected
     by the bug here (Thanks Andres)

  [Test Case]

   * Comment #42 contains a virtual test setup to understand the case but it 
 does NOT trigger the isse. That requires special switch HW that adds 
 VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a 
 customer site with such hardware being affected by this issue.

  [Regression Potential]

   * The only reference to VLAN tags on iPXE boot that we found was on iBFT
     boot for SCSI, we tested that in comment #34 and it still worked fine.
   * We didn't see such cases on review, but there might be use cases that
     made some unexpected use of the headers which are now stripped. But
     that seems wrong.

  [Other Info]

   * n/a

  ---

  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the 

[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

2019-01-15 Thread Brian Murray
Hello Dean, or anyone else affected,

Accepted apt into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.7.1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Cosmic)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in linux-meta source package in Xenial:
  New
Status in linux-meta-hwe source package in Xenial:
  New
Status in apt source package in Bionic:
  Fix Committed
Status in linux-meta source package in Bionic:
  New
Status in linux-meta-hwe source package in Bionic:
  New
Status in apt source package in Cosmic:
  Fix Committed
Status in linux-meta source package in Cosmic:
  New
Status in linux-meta-hwe source package in Cosmic:
  New
Status in apt source package in Disco:
  Fix Released
Status in linux-meta source package in Disco:
  Triaged
Status in linux-meta-hwe source package in Disco:
  Triaged

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  

[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

2019-01-15 Thread Brian Murray
Hello Vern, or anyone else affected,

Accepted ipxe into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ipxe/1.0.0+git-20180124.fbe8c52d-
0ubuntu4.1 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Fix Released
Status in ipxe-qemu-256k-compat package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in ipxe source package in Trusty:
  Won't Fix
Status in ipxe source package in Xenial:
  Won't Fix
Status in ipxe source package in Bionic:
  Incomplete
Status in ipxe source package in Cosmic:
  Fix Committed
Status in ipxe source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * VLAN 0 is special (for QoS actually, not a real VLAN)
   * Some components in the stack accidentally strip it, so does ipxe in
     this case.
   * Fix by porting a fix that is carried by other distributions as upstream
     didn't follow the suggestion but it is needed for the use case affected
     by the bug here (Thanks Andres)

  [Test Case]

   * Comment #42 contains a virtual test setup to understand the case but it 
 does NOT trigger the isse. That requires special switch HW that adds 
 VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a 
 customer site with such hardware being affected by this issue.

  [Regression Potential]

   * The only reference to VLAN tags on iPXE boot that we found was on iBFT
     boot for SCSI, we tested that in comment #34 and it still worked fine.
   * We didn't see such cases on review, but there might be use cases that
     made some unexpected use of the headers which are now stripped. But
     that seems wrong.

  [Other Info]

   * n/a

  ---

  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable 

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2019-01-09 Thread Brian Murray
I tested this upgrade process and it worked for me, setting to
verification-done.

bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ grep 
"release-upgrader version" /var/log/dist-upgrade/main.log 
2019-01-09 15:50:20,150 INFO release-upgrader version '18.10.11.3' started
bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ cat 
/etc/X11/xorg.conf
Section "Device"
Identifier "nvidia"
EndSection
bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ cat 
/etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.10


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

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  --
  Users who have manually configured an xorg.conf file with nvidia enabled as a 
driver will be surprised to have disabled on upgrade to a new release of Ubuntu 
and won't have a graphical display.

  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.

  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf

  When testing the release-upgrader from -proposed you'll need to use
  the -p switch to get the right tarball. Additionally, you'll want to
  add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia
  defaults to True instead of False (line 106) this'll simulate the
  nvidia driver being loaded.

  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.

  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2019-01-09 Thread Brian Murray
** Description changed:

  Impact
  --
- Users who have manually configured and xorg.conf file with nvidia enabled as 
a driver will be surprised to have disabled on upgrade to a new release of 
Ubuntu and won't have a graphical display.
+ Users who have manually configured an xorg.conf file with nvidia enabled as a 
driver will be surprised to have disabled on upgrade to a new release of Ubuntu 
and won't have a graphical display.
  
  Test Case
  -
  If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.
  
  1) Run do-release-upgrade (use -d if upgrading to disco)
  2) Cancel the upgrade
  3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
  4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
  5) run ./$target-release-name --frontend DistUpgradeViewText
  6) Observe the Driver line is commented out of xorg.conf
  
  When testing the release-upgrader from -proposed you'll need to use the
  -p switch to get the right tarball. Additionally, you'll want to add a
  step 4.5 where you modify xorg_fix_proprietary.py so nvidia defaults to
  True instead of False (line 106) this'll simulate the nvidia driver
  being loaded.
  
  Regression Potential
  
  This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.
  
  Original Description
  
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:
  
  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection
  
  As the installtion routine backuped my xorg.conf I could verify that the
  line hadn't been commented out before upgrading. Removing the "#" solved
  the problem.
  
  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash 
vt.handoff=1SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  

[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

2019-01-08 Thread Brian Murray
Hello Hui, or anyone else affected,

Accepted alsa-lib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.3-5ubuntu0.2 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in alsa-lib source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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


[Kernel-packages] [Bug 1458204] Update Released

2019-01-08 Thread Brian Murray
The verification of the Stable Release Update for update-notifier has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/unattended-upgrades/+bug/1458204/+subscriptions

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

[Kernel-packages] [Bug 1809934] Re: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot

2019-01-07 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot

Status in linux package in Ubuntu:
  New

Bug description:
  CPU: AMD Ryzen 5 2400G / AMD Ryzen 3 2200G
  Version: Ubuntu 18.04.1 Desktop (AMD64)
  Kernel: 4.15.0-43 generic
  Mainboard: ASUS Prime X370-Pro (4207), ASRock B450 Pro4 (1.80), MSI B350 
Tomahawk (7A34v1K), Gigabyte GA-AB350M-Gaming3 (F24c)

  Detailed information:
  AMD AGESA version "PinnaclePI-AM4 1.0.0.6" based firmware is released by many 
major mainboard manufacturers lately.
  However, this 1.0.0.6 based firmware with Raven Ridge processors (2200G, 
2400G and more) cause system hangs on boot if a system is running 4.15.0 kernel.

  If install kernel version 4.18.0-13-generic from "linux-image-generic-
  hwe-18.04-edge" has no issue.

  Here is boot messages output (dumped via serial port and truncated):

  [4.385021] [drm] ring test on 5 succeeded in 3 usecs
  [4.385030] [drm] ring test on 6 succeeded in 2 usecs
  [4.385035] [drm] ring test on 7 succeeded in 1 usecs
  [4.385044] [drm] ring test on 8 succeeded in 2 usecs
  [4.385090] [drm] ring test on 10 succeeded in 2 usecs
  [5.406001] clocksource: timekeeping watchdog on CPU2: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [5.406002] clocksource:   'hpet' wd_now: 5152d87 
wd_last: 40b14df mask: 
  [5.406004] clocksource:   'tsc' cs_now: f4c92bc9d 
cs_last: ebf5adbce mask: 
  [5.406006] tsc: Marking TSC unstable due to clocksource watchdog
  [5.406014] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [5.406015] sched_clock: Marking unstable (5406009219, 0)<-(5548358599, 
-142345214)
  [7.906021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [9.156104] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: writing 
more dwords to the ring than expected!
  [   11.656035] ata2.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133
  [   32.204004] watchdog: BUG: soft lockup - CPU#2 stuck for 21s! 
[kworker/2:1:60]
  [   32.204005] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid 
hid amdkfd amd_iommu_v2 amdgpu(+) chash i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect uas sysimgblt fb_sys_fops drm r8169 usb_storage 
i2c_piix4 mii ahci libahci wmi video gpio_a

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

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


[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-21 Thread Brian Murray
** Description changed:

+ Impact
+ --
+ Users who have manually configured and xorg.conf file with nvidia enabled as 
a driver will be surprised to have disabled on upgrade to a new release of 
Ubuntu and won't have a graphical display.
+ 
+ Test Case
+ -
+ If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.
+ 
+ 1) Run do-release-upgrade (use -d if upgrading to disco)
+ 2) Cancel the upgrade
+ 3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
+ 4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
+ 5) run ./$target-release-name --frontend DistUpgradeViewText
+ 6) Observe the Driver line is commented out of xorg.conf
+ 
+ When testing the release-upgrader from -proposed you'll need to use the
+ -p switch to get the right tarball. Additionally, you'll want to add a
+ step 4.5 where you modify xorg_fix_proprietary.py so nvidia defaults to
+ True instead of False (line 106) this'll simulate the nvidia driver
+ being loaded.
+ 
+ Regression Potential
+ 
+ This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.
+ 
+ Original Description
+ 
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:
  
  Section "Device"
- Identifier "nvidia"
+ Identifier "nvidia"
  #Driver "nvidia"
- BusID "PCI:10@0:0:0"
- Option "ConstrainCursor" "off"
+ BusID "PCI:10@0:0:0"
+ Option "ConstrainCursor" "off"
  EndSection
  
  As the installtion routine backuped my xorg.conf I could verify that the
  line hadn't been commented out before upgrading. Removing the "#" solved
  the problem.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
+ ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
-  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
+  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
-  bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
-  nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
-  nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
+  bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
+  bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
+  nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
+  nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
-Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
+    Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
- SourcePackage: xorg
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash 
vt.handoff=1SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-21 Thread Brian Murray
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  New

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-19 Thread Brian Murray
** Also affects: ubuntu-release-upgrader (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  New
Status in ubuntu-release-upgrader source package in Cosmic:
  New

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1806532] Please test proposed package

2018-12-19 Thread Brian Murray
Hello Hui, or anyone else affected,

Accepted alsa-lib into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.6-1ubuntu1.2 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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


[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

2018-12-18 Thread Brian Murray
Hello Hui, or anyone else affected,

Accepted alsa-lib into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.6-1ubuntu1.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: alsa-lib (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

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

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


[Kernel-packages] [Bug 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

2018-12-18 Thread Brian Murray
** Description changed:

  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.
  
  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
- More tests have been done on amd64 and ppc64el, including memory commands, bt.
+ More tests will be done with the version of the package from -proposed on 
amd64 and ppc64el, including memory commands, and bt.
  
  [Regression Potential]
- New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.
+ New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing is desirable.
  
  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the regression.
  But live analysis won't be possible in that case.
  
  -
  
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---
  
  Ubuntu 18.04: "ipcs" command fails with error "invalid structure member
  offset" in crash prompt.
  
  ---Environment--
  
  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML
  
  ---Uname output---
  
  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
  
  ---Steps to reproduce--
  
  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump
  
  ---Logs
  
  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#
  
  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.
  
  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...
  
    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)
  
  crash> ?
  
  *  files  mach   repeat timer
  alias  foreachmodrunq   tree
  ascii  fuser  mount  search union
  bt gdbnetsetvm
  btop   help   p  sigvtop
  devipcs   ps struct waitq
  disirqpte   

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-17 Thread Brian Murray
The xorg apport package hook checks /proc/modules for the presence of
nvidia which seems better than looking multiple places for an nvidia .so
file, so let's convert xorg_fix_proprietary.py to check for that.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-release-upgrader (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-vid

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-14 Thread Brian Murray
Hey, thanks for helping out with the log file. Could you also add
'/var/log/dist-upgrade/xorg_fixup.log' to your bug report?  Thanks
again!

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-14 Thread Brian Murray
And it looks like this is something I removed last year, here's the
changelog entry.

  * build-tarball.sh: Stop updating ubuntu-drivers-obsolete.pkgs since it
isn't needed any more see Launchpad bug 1682291 for details.

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-14 Thread Brian Murray
Looking at the log file we can see the following:

2018-05-21 09:55:56,514 DEBUG nvidiaUpdate()
2018-05-21 09:55:58,109 INFO no old nvidia driver installed, installing no new

Then looking at DistUpgradeCache from ubuntu-release-upgrader there is
this:

 540 # get new detection module and use the modalises files
 541 # from within the release-upgrader
 542 nv = NvidiaDetection(obsolete="./ubuntu-drivers-obsolete.pkgs")
 543 #nv = NvidiaDetection()
 544 # check if a binary driver is installed now
 545 for oldDriver in nv.oldPackages:
 546 if oldDriver in self and self[oldDriver].is_installed:
 547 self.mark_remove(oldDriver, "old nvidia driver")
 548 break
 549 else:
 550 logging.info("no old nvidia driver installed, installing 
no new")
 551 return False

Unfortunately, the dist-upgrader tarball doesn't actually have "ubuntu-
drivers-obsolete.pkgs" in it so nv.oldPackages is always empty and no
old nvidia driver will be detected.

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: 

[Kernel-packages] [Bug 1808069] Re: Init corrupted when upgrading to 4.15.0-42

2018-12-12 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Init corrupted when upgrading to 4.15.0-42
+ Init corrupted when running 4.15.0-42

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  New

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

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

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


[Kernel-packages] [Bug 1787405] Update Released

2018-12-11 Thread Brian Murray
The verification of the Stable Release Update for libvirt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released
Status in libvirt source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Committed
Status in libvirt source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in qemu source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * The ability to pass through more cryptographic capabilities is a very
     important feature for users of s390x as virtualization platform.
     Its availability upstream now and its backport in this bug allows to
     exploit the crypto cards as new HW for these virtualization use
     cases.

   * This falls under both "other safe cases" SRU exceptions:
  - For Long Term Support releases we regularly want to enable new
    hardware ...
  - For Long Term Support releases we sometimes want to introduce new
    features. They must not change the behaviour on existing
    installations ...

   * This bug has three main components:
     - kernel (ability to do all of this)
     - qemu (add feature to exploit the new code)
     - libvirt (make the feature user consumable)

  [Test Case]

   * In general this consists of a few steps
 - get the updated kernel/qemu/libvirt
 - mask the card & domains from the usual driver
 - load vfio-ap
 - assign card to vfio-ap
 - prepare a guest
 - configure a guest to use the card

   * See comment #66 how to do all of that in detail

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/66

  [Regression Potential]

   * The changes are mostly s390x only and adding a new feature so
     regressions to existing components should be low. But to backport it
     slight changes to the MDEV handling had to be applied as well.
     The potential regressions I can see are in that MDEV handling if one
     of the backports would be bad.
     Fortunately we know that without the related libvirt fixes we added
     here using MDEVs didn't work at all yet, and people very rarely use
     qemu without libvirt for anything else than experiments.
     Therefore I'm confident that even if there would be a flaw in the
     MDEV changes no one is hugely relying on it.

  [Other Info]

   * n/a

  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: 

[Kernel-packages] [Bug 1807605] Re: Could not report Linux error

2018-12-10 Thread Brian Murray
** Package changed: apport (Ubuntu) => linux (Ubuntu)

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

Title:
  Could not report Linux error

Status in linux package in Ubuntu:
  New

Bug description:
  System tried to update and got an error due to the defective superspec
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-12-generic 4.18.0-12.13
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 3284 F pulseaudio
   /dev/snd/controlC0:  robert 3284 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Dec  9 12:41:11 2018
  InstallationDate: Installed on 2018-11-30 (9 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-12-generic N/A
   linux-backports-modules-4.18.0-12-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  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/1807605/+subscriptions

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


[Kernel-packages] [Bug 1807429] Re: 4.15.0-42-generic intel_iommu=on crash on boot

2018-12-10 Thread Brian Murray
** Project changed: errors => linux (Ubuntu)

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

Title:
  4.15.0-42-generic intel_iommu=on crash on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  New Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-42-generic x86_64) installation
  dist-upgraded as of Fri Dec  7 17:49:07 GMT 2018
  running Dell R440 with Dell Boss card as boot drive

  nano /etc/default/grub
  ->GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on"

  update-grub
  reboot

  Error on boot:

  gave up waiting for root file system
  missing modules
  Alert UUID= does not exist dropping to shell

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

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


[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-12-05 Thread Brian Murray
Could you provide your /var/log/dist-upgrade/main.log file from the
upgrade to Ubuntu 18.04?  Thanks in advance.

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1806845] Re: The unsigned vf->num_mac will be decreased to below zero and cause the VF port not working

2018-12-05 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  The unsigned vf->num_mac will be decreased to below zero and cause the
  VF port not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The unsigned vf->num_mac in Ubuntu18.04.1 LTS i40e driver 2.1.14-k
  will be decreased to below zero when VF is trying to delete the MAC
  address which is added by PF and then add a new MAC address. And after
  this issue happens, VF won't be able to send/receive packets, and
  excepting for broadcast address, mac_filter_hash is empty in dumped
  VSI info.

  Ubuntu18.04.1 LTS kernel: 4.15.0-38-generic
  i40e driver: 2.1.14-k
  i40evf driver: 3.0.1-k

  Actual results:
  The unsigned vf->num_mac should decrease to below zero. The VF port doesn't 
work.

  Expected results:
  The unsigned vf->num_mac range is from 0 to 65535;
  or the vf is not allowed to delete the MAC addr which is added by PF

  Corresponding Patch is required for resolving this i40e driver issue

  i40e: Prevent deleting MAC address from VF when set by PF
  https://patchwork.ozlabs.org/patch/963036/

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

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


[Kernel-packages] [Bug 1755490] Please test proposed package

2018-12-04 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted hwdata into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/hwdata/0.249-1ubuntu1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  Fix Committed
Status in hwdata source package in Trusty:
  Fix Committed
Status in unity-settings-daemon source package in Trusty:
  Invalid
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-12-04 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted gnome-desktop3 into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.8.4-0ubuntu3.3 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-desktop3 (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

** Changed in: hwdata (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  Fix Committed
Status in hwdata source package in Trusty:
  Fix Committed
Status in unity-settings-daemon source package in Trusty:
  Invalid
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

2018-12-03 Thread Brian Murray
Hello Daniel, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.0 in a few hours, and then
in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/unattended-upgrades/+bug/1458204/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

2018-12-03 Thread Brian Murray
** Changed in: unattended-upgrades (Ubuntu Artful)
   Status: Confirmed => Won't Fix

** Changed in: update-notifier (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/unattended-upgrades/+bug/1458204/+subscriptions

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


[Kernel-packages] [Bug 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'

2018-11-29 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Status: New => Incomplete

** Changed in: kerneloops (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Missing the 'Call Trace' with the cases of 'KernelOops'

Status in apport package in Ubuntu:
  Incomplete
Status in kerneloops package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I am working with these two reports:

  * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
  https://bugs.launchpad.net/bugs/1796385

  * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  https://bugs.launchpad.net/bugs/1797538

  And the file: 'OopsText.txt' does not appear in the 'Call Trace'.

  Others:
  https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3
  "The bug in lauchpad, unless I am missing something, provides not a single 
actionable traceback. I don't think it is even possible to identify where 
exactly the CPU hangs unless additional information is provided. There is no 
traceback in dmesg, and OopsText doesn't include it either.

  Given that, it is not possible to identify the responsible subsystem,
  much less to fix the underlying problem. The only thing we can say for
  sure is that it is _not_ a watchdog driver problem."

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu11
  Uname: Linux 4.18.13-gnu x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 16:12:58 2018
  InstallationDate: Installed on 2017-10-13 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1755490] Please test proposed package

2018-11-28 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted hwdata into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/hwdata/0.290-1ubuntu0.18.10.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1755490] Please test proposed package

2018-11-28 Thread Brian Murray
Hello Dariusz, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-28 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted hwdata into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/hwdata/0.267-1ubuntu2
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in hwdata source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in hwdata source package in Cosmic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1805670] Re: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad

2018-11-28 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues
  ex. suspend, touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some background information:
  I have a new Ubuntu 18.04 installation that did not go too well.
  The Live-USB installation would hang with ACPi related errors.
  I finally installed (barring a GRUB install error) using the acpi=off kernel 
flag.
  I also tested with acpi=force and no acpi settings (only worked after the 
last kernel update).
  I report here with
  - no changes in the kernel parameters
  - no changes in BIOS except of graphics set to hybrid (Nvidia + Intel) 
otherwise I could not get it to work

  I am following the indications here:
  https://wiki.ubuntu.com/DebuggingACPI

  So here is the initial information I have (kernel version, kernel
  parameters, ACPI errors):

  ..

  uname -a
  Linux gandalf 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=82d8b6b9-1f12-4651--3639a6b76683 ro quiet splash vt.handoff=1

  dmesg | grep -i acpi | grep -i error
  [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup 
failure, AE_NOT_FOUND (20170831/dswload-210)
  [0.00] ACPI Error: 1 table load failures, 19 successful 
(20170831/tbxfload-246)
  [0.164845] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds 
size of target Buffer (64 bits) (20170831/dsopcode-235)
  [0.164874] ACPI Error: Method parse/execution failed \_SB._OSC, 
AE_AML_BUFFER_LIMIT (20170831/psparse-550)
  [3.528032] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.528042] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [3.529831] ACPI Error: Method parse/execution failed 
\_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550)
  [3.529840] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103)
  [4.610629] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.610635] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611513] ACPI Error: Method parse/execution failed \_TZ.GETP, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [4.611518] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, 
AE_AML_PACKAGE_LIMIT (20170831/psparse-550)
  [8.206279] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
85bce4f4 (20170831/exresop-593)
  [8.206309] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.206315] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210629] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
352a9487 (20170831/exresop-593)
  [8.210660] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.210666] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214527] ACPI Error: Needed [Buffer/String/Package], found [Integer] 
88ce12bb (20170831/exresop-593)
  [8.214555] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.214562] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_TYPE (20170831/psparse-550)
  [8.231122] ACPI Error: Attempt to CreateField of length zero 
(20170831/dsopcode-168)
  [8.231147] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)
  [8.231154] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, 
AE_AML_OPERAND_VALUE (20170831/psparse-550)

  ..

  I have also added the following outputs:

  sudo lspci -vvnn >> report.txt

  sudo dmidecode > dmidecode.txt

  The kern.log after a suspend and resume.

  

  Some weird behavior I have noticed:

  . The Live-USB pendrive allowed me to use the touchpad when testing and 
installing Ubuntu
  . The current kernel does not allow me to use the touchpad
  . After I resume, the touchpad can be used
  . I cannot resume with the builtin At keyboard or touchpad
  . The dock (via Thunderbolt) gives me access to a mouse and keyboard that I 
use to resume
  . I have related graphics driver issue but do not know if they are related

  Is their 

[Kernel-packages] [Bug 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'

2018-11-28 Thread Brian Murray
Could you provide the full kern.log file with an OOPS in it? Thanks in
advance.

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

Title:
  Missing the 'Call Trace' with the cases of 'KernelOops'

Status in apport package in Ubuntu:
  New
Status in kerneloops package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I am working with these two reports:

  * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
  https://bugs.launchpad.net/bugs/1796385

  * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  https://bugs.launchpad.net/bugs/1797538

  And the file: 'OopsText.txt' does not appear in the 'Call Trace'.

  Others:
  https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3
  "The bug in lauchpad, unless I am missing something, provides not a single 
actionable traceback. I don't think it is even possible to identify where 
exactly the CPU hangs unless additional information is provided. There is no 
traceback in dmesg, and OopsText doesn't include it either.

  Given that, it is not possible to identify the responsible subsystem,
  much less to fix the underlying problem. The only thing we can say for
  sure is that it is _not_ a watchdog driver problem."

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu11
  Uname: Linux 4.18.13-gnu x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 16:12:58 2018
  InstallationDate: Installed on 2017-10-13 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-28 Thread Brian Murray
** Changed in: hwdata (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1755490] Please test proposed package

2018-11-28 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted hwdata into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/hwdata/0.267-1ubuntu1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-28 Thread Brian Murray
Ah, my bad the system I was on didn't have disco in its sources.list
file.

** Changed in: hwdata (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'

2018-11-27 Thread Brian Murray
This actually looks like an issue with kerneloops which parses dmesg for
Call Trace.

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

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

** Changed in: kerneloops (Ubuntu)
   Status: New => Triaged

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

Title:
  Missing the 'Call Trace' with the cases of 'KernelOops'

Status in apport package in Ubuntu:
  New
Status in kerneloops package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I am working with these two reports:

  * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
  https://bugs.launchpad.net/bugs/1796385

  * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  https://bugs.launchpad.net/bugs/1797538

  And the file: 'OopsText.txt' does not appear in the 'Call Trace'.

  Others:
  https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3
  "The bug in lauchpad, unless I am missing something, provides not a single 
actionable traceback. I don't think it is even possible to identify where 
exactly the CPU hangs unless additional information is provided. There is no 
traceback in dmesg, and OopsText doesn't include it either.

  Given that, it is not possible to identify the responsible subsystem,
  much less to fix the underlying problem. The only thing we can say for
  sure is that it is _not_ a watchdog driver problem."

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu11
  Uname: Linux 4.18.13-gnu x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 16:12:58 2018
  InstallationDate: Installed on 2017-10-13 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-27 Thread Brian Murray
I see an hwdata upload for Xenial but I don't see the change to GSM /
Goldstar Company as having been done in Disco. Is there a reason it
hasn't been updated there too?

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in unity-settings-daemon source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1755490] Update Released

2018-11-27 Thread Brian Murray
The verification of the Stable Release Update for unity-settings-daemon
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Released
Status in unity-settings-daemon source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1805188] Re: Installmedia; Failing boot: "ACPI Error: Method parse/execution failed"

2018-11-27 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Installmedia; Failing boot: "ACPI Error: Method parse/execution
  failed"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: Thinkpad X1 Extreme (20MF000TGE)
  State: Initial Win10 installation.

  Trying to install *any* recent desktop version of ubuntu, but also
  live image fails brutally, due to (PCIO) ACPI errors:

  [0.452142] ACPI Error: Method parse/execution failed 
\_SB.PCIO.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20180531/psparse-516)
  [0.452168] ACPI Error: Method execution failed \_SB.PCIO.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20180531/uteval-69)
  [0.455124] ACPI Error: Method parse/execution failed 
\_SB.PCIO.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20180531/psparse-516)
  [0.455146] ACPI Error: Method execution failed \_SB.PCIO.SPI2.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20180531/uteval-69)

  The error occurs on 18.10. desktop usb installation media: It doesn't matter 
which USB stick on the right side is used. I was neither able to boot the live 
system of this version in efi mode nor in legacy bios mode. Medium check 
completed successfully. SHA256-sum of the install media is 
"818affdaea8d38bbbe620009bfa788a7cbc583c7c61c2d278f61dd3c43e030a0" (which is 
correct!).
  Directly choosing installation in the boot menu does just show a black screen.

  I also tried 18.04.1 LTS to double check: This install image does not
  boot either, but the error is just shown briefly, so I cannot tell if
  this is indeed the same error. Selfchecking this media freezes the
  system at some point during the process. Also this media produces the
  correct sha256-sum.

  I can confirm this for two different USB sticks: SanDisk Ultra USB3.0
  (16GB) and some unknown TOSHIBA  model.

  Update:
  Okay. A BIOS update fixed something: at least it boots now into live...

  Please ask questions, if something is unclear or if you want me to
  test/do something...

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

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


[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-26 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted unity-settings-daemon into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unity-settings-daemon/15.04.1+16.04.20160701-0ubuntu3 in a few hours,
and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unity-settings-daemon (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Incorrect information about display shown in gnome/unity-control-
  center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-settings-daemon source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain its real diagonal or model name (if dimensions 
are not availabe).

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

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


[Kernel-packages] [Bug 1804505] Re: Kubuntu 18.04.01 - Ryzen 2400G / AMDGPU - Random system freezes

2018-11-26 Thread Brian Murray
** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Kubuntu 18.04.01 - Ryzen 2400G / AMDGPU - Random system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am experiencing some stray lockups which are most likely related to
  AMDGPU. There is no apparent logic in the pattern with wich the system
  hangs and I cannot provide any steps to reproduce the problem. One
  time it happened as I clicked a link in Firefox, new tab opened and
  the system froze. Another time, Firefox was not open and I was about
  to edit a text file by clicking "F4 Edit" in Krusader and the system
  froze. When the system freezes, it is completely unresponsive and
  there are no other options than to reset and reboot. The system
  generates no error reports as far as I can figure out and the only
  apparent info are some entries in the syslog. I have appended relevant
  info below, if further info may be needed please ask :)

  [b]inxi -Fz[/b]

  System:Host: computername Kernel: 4.19.1-041901-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.12.6
 Distro: Ubuntu 18.04.1 LTS
  Machine:   Device: desktop Mobo: ASUSTeK model: PRIME A320M-A v: Rev X.0x 
serial: N/A
 UEFI: American Megatrends v: 4023 date: 08/20/2018
  Batteryhidpp__0: charge: 80% condition: NA/NA Wh
  CPU:   Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) 
cache: 2048 KB
 clock speeds: max: 3600 MHz 1: 1454 MHz 2: 1418 MHz 3: 1419 MHz 4: 
1419 MHz 5: 1419 MHz 6: 1419 MHz
 7: 1436 MHz 8: 1582 MHz
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon Vega 8 Mobile]
 Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: 
modesetting,fbdev,vesa,radeon)
 Resolution: 1680x1050@59.88hz
 OpenGL: renderer: AMD RAVEN (DRM 3.27.0 / 4.19.1-041901-generic, 
LLVM 6.0.0) version: 4.5 Mesa 18.0.5
  Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: 
snd_hda_intel
 Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: 
snd_hda_intel
 Sound: Advanced Linux Sound Architecture v: k4.19.1-041901-generic
  Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller driver: r8169
 IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: 
  Drives:HDD Total Size: 250.1GB (26.2% used)
 ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_250GB size: 250.1GB
  Partition: ID-1: / size: 228G used: 61G (29%) fs: ext4 dev: /dev/nvme0n1p2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: N/A mobo: N/A gpu: 26.0
 Fan Speeds (in rpm): cpu: 0
  Info:  Processes: 232 Uptime: 22 min Memory: 1176.8/6960.8MB Client: 
Shell (bash) inxi: 2.3.56 

  
  [b]SYSLOG[/b]

  Prior to the first relevant entry posted here is a CRON entry @
  13:18:01 which seems unrelated to the issue. All entries where
  preceeded with "Nov 21 13:23:13 computername kernel: ":

  [ 4335.012512] gmc_v9_0_process_interrupt: 13 callbacks suppressed
  [ 4335.012516] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 
vmid:1 pasid:32768, for process Xorg pid 863 thread amdgpu_cs:0 pid 870
  [ 4335.012516] )
  [ 4335.012521] amdgpu :08:00.0:   at address 0x000101c0d000 from 27
  [ 4335.012523] amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [ 4335.012530] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 
vmid:1 pasid:32768, for process Xorg pid 863 thread amdgpu_cs:0 pid 870
  [ 4335.012530] )
  [ 4335.012532] amdgpu :08:00.0:   at address 0x000101c11000 from 27
  [ 4335.012534] amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [ 4335.012540] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 
vmid:1 pasid:32768, for process Xorg pid 863 thread amdgpu_cs:0 pid 870
  [ 4335.012540] )
  [ 4335.012542] amdgpu :08:00.0:   at address 0x000101c29000 from 27
  [ 4335.012544] amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [ 4335.012550] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 
vmid:1 pasid:32768, for process Xorg pid 863 thread amdgpu_cs:0 pid 870
  [ 4335.012550] )
  [ 4335.012552] amdgpu :08:00.0:   at address 0x000101c2d000 from 27
  [ 4335.012554] amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [ 4335.012560] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 
vmid:1 pasid:32768, for process Xorg pid 863 thread amdgpu_cs:0 pid 870
  [ 4335.012560] )
  [ 4335.012562] amdgpu :08:00.0:   at address 0x000101c1 from 27
  [ 4335.012563] amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [ 4335.012569] amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 

[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in unity-control-center

2018-11-20 Thread Brian Murray
Hello Dariusz, or anyone else affected,

Accepted unity-settings-daemon into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unity-settings-daemon/15.04.1+18.04.20180413-0ubuntu1.2 in a few hours,
and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unity-settings-daemon (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Incorrect information about display shown in unity-control-center

Status in hwdata package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Bionic:
  Fix Committed
Status in unity-settings-daemon source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * There is a number of display devices that misuse the width & height field 
in EDID. Instead of real size in centimeters it contains encoded aspect ratio 
(e.g. 1600x900, 16x10, 160x90).
  This leads to incorrect calculation of diagonal for the purpose of e.g. Unity 
settings app.

  [Test Case]

   1. Connect a display device that provides incorrect EDID data (e.g. LG 
49UB850T-DA TV).
   2. Open the Displays section of Unity settings.
   3. Look for the name of the newly connected display in the settings window.

  Expected result:
  Display name should contain it's real diagonal.

  Actual result:
  Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" 
display).

  [Regression Potential]

   * This affects the way the display name will be formatted for any
  software using unity-settings-daemon. If anything is testing/comparing
  display names - it may fail.

  [Other Info]

  * Original bug description:

  After connecting a LG 49UB850T-DA TV the following information is
  displayed in the unity-control-center: Goldstar Company Ltd 72"

  It's misleading since neither the company name nor the diagonal
  matches.

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

-- 
Mailing list: https://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   3   4   5   6   7   8   9   >